![]() |
|
#13
|
|||
|
|||
|
HW breakpoints won't help you if the program performs self-checksums in memory. What you really want to do is diff runtime traces:
1) Record a trace of running the unmodified binary 2) Record a trace of running the modified binary 3) See where they differ. This yields one (possibly many) program location which does "the check(s)". As for collecting traces, use your favourite debugger (x64dbg, ollydbg, IDA) or dynamic binary instrumentation tool (DynamoRIO, PIN). |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Identify an unknown 64 bit Packer | Kurapica | General Discussion | 1 | 07-06-2021 01:05 |
| Help identify crypto | The Old Pirate | General Discussion | 5 | 12-27-2014 04:15 |
| Trying to identify crypto algorithm | SiNTAX | General Discussion | 4 | 06-17-2010 03:23 |