![]() ![]() Should work if the person cracking doesn't know which hwid he should send or what the client should receive. Send the hardware id to a server which compares them and sends back the hack module or some other data the hack needs to work. Yes, can you explain some ways to fix this issue? Maybe, ways to secure this further. You may want to move opcodes around.Īgain making certain to employ integrity checks, and the like. Lastly, if you absolutely must, compile your code in another architecture and write a VM to support that. Otherwise you're being debugged and that should affect code flow or key generation. ![]() Naturally you should make certain your handler is the at the top. One example would be registering your own exception handler. These feed into your algorithm to generate additional decrypt keys each step along the way. You could also use the status of the flags register, or rdtsc, or any number of methods to help in debugger detection. Continuing on, I don't see why you wouldn't employ a code checksum to also generate further decryption keys. Think taking a SHA 512 hash and using that to generate a nice AES 256 key. If the auth is based on HWID to generate a decryption key using secure algorithms aside from faking your HWID, I don't see any expeditious way to crack it, that is assuming you are on a different computer than the one the binary was signed for. This, to inform you there are many ways to crack HWID without a debugger. When i cracked a crappy hack with HWID protection i didn't even needed to use Olly or IDA. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |