![]() īTW: Modifying the NSIS source codes and "randomizing" some of it's data structures would be one method of obfuscation. This cannot be prevented without special hardware mechanisms (like a TPM), it can only be made more difficult by using techniques of "obfuscation". Guess why those new "unbreakable" Copy Protection systems like AACS (Blue Ray Disc) have been broken that fast! They didn't crack the protection itself, they simply grabbed the "secret" keys from memory while playing the disc in a legitimate player. ![]() So somebody could do a memory dump and obtain your string. But even if you mange to keep your key a secret (the key must be stored somewhere in the EXE file too), still the string would be in memory at runtime. ![]() Of course you could try to encrypt the string and decrypt it at only at runtime. I'll study threads that Red Wine posted.You cannot protect strings! If your installer "knows" (uses) the string, then it must be stored somewhere in the EXE file. Only thing I was afraid was strings (which are in disassembly).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |