https://github.com/codingo/cracknet

A .net Crackme Challenge made for the SecTalks Brisbane 2017 Capture the Flag Event. Writeup/solution included.
https://github.com/codingo/cracknet

capture-the-flag challenge challenges ctf ctf-challenges ctf-solutions ctf-writeups decompile ida radare2 reverse-engineering security vulnerable vulnerable-application writeup

Last synced: about 1 month ago
JSON representation

A .net Crackme Challenge made for the SecTalks Brisbane 2017 Capture the Flag Event. Writeup/solution included.

• Host: GitHub
• URL: https://github.com/codingo/cracknet
• Owner: codingo
• License: mit
• Created: 2017-04-10T04:38:41.000Z (about 8 years ago)
• Default Branch: master
• Last Pushed: 2017-10-02T22:42:39.000Z (over 7 years ago)
• Last Synced: 2025-04-20T09:59:18.519Z (about 2 months ago)
• Topics: capture-the-flag, challenge, challenges, ctf, ctf-challenges, ctf-solutions, ctf-writeups, decompile, ida, radare2, reverse-engineering, security, vulnerable, vulnerable-application, writeup
• Language: C#
• Homepage: https://www.codingo.com.au
• Size: 162 KB
• Stars: 23
• Watchers: 9
• Forks: 11
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# cracknet

A .net Crackme Challenge made for the SecTalks Brisbane 2017 CTF Event.

[![Twitter](https://img.shields.io/badge/twitter-@codingo__-blue.svg)](https://twitter.com/codingo_)

***Intended binary for challenge***: https://github.com/codingo/cracknet/blob/master/ctf.sectalks_bne.crackme/bin/Debug/cracknet.exe

Note that this is a debug build and not a release build, due to compiler instructions. Only the executable needs to be included for the challenge.

## Source Code Notes

Built with v4.5.2 of .Net (https://www.microsoft.com/en-au/download/details.aspx?id=42642)

## Writeup / Solution

A writeup explaining one solution path for this binary can be found here: https://codingo.github.io/reverse-engineering/ctf/2017/07/25/Decompiling-CSharp-By-Example-with-Cracknet.html

Further solution notes (including alternative ways to solve this) can be found as code comments within __Program.cs__.