| APicturePerfectPassword |
@legendsciber Thanks for your comment you nailed it. I wasnt sure whether i should use obfuscation and anti-debugging techniques. Personally i dont like having annoying unreadable code instead of a clear idea or challenge but i think the naming etc. gives too much away. What are your thoughts on this? |
2026-07-17 20:00 |
| Password or Payload? |
@Frantz04 Everything that UTF-8 interprets as a C3 Byte. It is enough to just let it return to give true back. |
2026-07-16 14:21 |
| Password or Payload? |
@illusionxxx as i wrote in the readme: you dont have to use an input injector. in fact you partially circumvent the challenge since you can use a broader byte palette than i intended to give you. |
2026-01-06 21:53 |
| Password or Payload? |
@mad38 there is even a rule on this site that states "Patching to make the binary print 'correct' or 'success' is generally not considered a valid solution for crackmes". this crackme is solvable by making a valid password. |
2026-01-06 14:00 |
| BeginnerFriendly |
|||||||||| |
2025-12-30 21:32 |
| Medium-Hard crackme |
I have to revise my previous comment. The problem is that the characters are displayed differently depending on the console code page. Under "850" it's ¦┐Ì¡£ý× and under "437" it's ▌┐▐¡£∞₧. With "UTF-8" it can't be solved by typing or copying the characters. I haven't tried it with other code pages, but you can either use Karabatik's approach or come up with something else. Have fun! |
2025-12-30 02:48 |
| Medium-Hard crackme |
For everyone whos solved it, but has problems with the password:
¦┐Ì¡£ý× |
2025-12-30 01:48 |