| There's a hook on the KiUserExceptionDispatcher which may make debugging a headache. Change the following 6 bytes into 0x00 to get rid of this hook and the random crashes it may cause: 0x401097, 0x4014B3, 0x40183C, 0x4019D9, 0x401F52, 0x401FE9 (all part of calls / jumps).
I can enter all serials and get the right message in time before the keygenme crashes so I don't consider this as an invalidation of the keygenme. |
==> |
| Sure, no problem. |
==> |
| You could say that figuring out why it crashes right away is part of the crackme unironically. Without giving too much away, figuring why it crashes is something you would need to do on Windows 10 as well ;) |
==> |
| @ToMKoL I see you're still active so I'll leave a message here. You suggested stronger name dependency and harder math equations. I did exactly that in my second keygenme. Should you decide to have a crack at it, please let me know. |
==> |
| Only tested on Win10 x64 - I got reports the crackme fails to open on Win7 altogether. |
==> |
| @ToMKoL Very nice! I remember now that I figured to ignore the delimiters under 0x32 because they cannot be typed, but you proved that one can make nicely use of those ;)
I'm currently thinking about ideas for #2. Anything you'd like me to implement beside making the user name more important? The CRC32 check btw, was that yay or nah? |
==> |
| Awesome to see some nice comments here after a while. @LordShy that's the right message, so unless you cheated, you've got the right combination ;)
@ToMKoL Well, shit, I thought I had that part covered. Even wrote a small python script to make sure.
@Xor0 / ToMKoL Can you tell what you think was the hardest part? I personally liked the way that there's one check you must / need to fail in order to get the right combination. |
==> |