| brainf*ck interpreter |
@Ploxied I'm sorry to hear that, but I really don't know what is causing the issue or how to help you... This program only uses stdio.h and pure c, and of course, was tested and working before uploading. All I can say is make sure you are using a windows device and this was tested on windows 10, and no crackme from me will ever be tested in any other os because of lack of tpm 2.0 in my laptop. Anyway, please tell me if you manage to fix your issue... |
2025-12-28 09:22 |
| Non-cryptographically secure hash (my first crackme!) |
@stardevreal patching (that is, changing the code/the executable) is not allowed on crackmes unless explicitly stated. That is literally in the website FAQ. |
2025-12-12 16:55 |
| Non-cryptographically secure hash (my first crackme!) |
Here are some known solutions to this crackme (solutions with invalid ascii characters will be written in hex):
"4530395016" (shout out to nightxyz for discovering this one)
"Hashed Password" (originally used to generate the hash)
"c{nnwc" (generated by my mobile phone in less than a secound without using brute force!! (check writeup for more details))
(hex) 02 10 09 02 1D 15 0D (also generated by my mobile phone in less than a secound, and also without brute force)
(hex) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c6 14 40 00 (abuses the buffer overflow to, from auth, return to grant_access instead of returning to main (check the crackme's source code))
|
2025-08-18 15:03 |
| Non-cryptographically secure hash (my first crackme!) |
Guys, I'll make it clear that the intended method to solve the crackme is not brute force! Please instead try to find the vulnerability in the code instead involving a buffer overflow. |
2025-08-18 14:57 |