Yes. Debugging and cracking often have a lot of common ground. For instance, say you want to disable the “so and so is typing” message sent by some chat clients, and you aren’t given an option to disable it *cough*slack*cough* you can use a debugger to find the specific point in the program where that message is written into a socket and replace the instruction bytes with 0x90 (no operation) using a hex editor.
You may not call that example “cracking” but it’s the same process of understanding the program flow and modifying it in a desired way.
can a debugger help in cracking ?
Yes. Debugging and cracking often have a lot of common ground. For instance, say you want to disable the “so and so is typing” message sent by some chat clients, and you aren’t given an option to disable it *cough*slack*cough* you can use a debugger to find the specific point in the program where that message is written into a socket and replace the instruction bytes with 0x90 (no operation) using a hex editor.
You may not call that example “cracking” but it’s the same process of understanding the program flow and modifying it in a desired way.
Awesome !
I guess function names are scrambled in the binary. That might make tracing a bit hexy.
I couldn’t find this article and thought it was a cool read so I put this here.