![]() ![]() ![]() You know, for small software companies or single programmers the logic behind the software protection nowadays is quite simple: Regarding to skipping the validation code can the cracker release a program to force my application to skip validation? any hints guys? I can merge the license validation inside the code so no calculation or keygen can crack it since the user dont enter anything and im not doing any calculation other than encrypting the hardware serial numbers and compare it with what I fetched from the client PC, this would be a good point to protect and im wondering if what im doing is right, I know that all programs can be cracked, but I'm trying to make it as hard as possible, since my clients are limited. ![]() Is that safe to use or maybe someone be able to change the XXXXX and rebuild the EXE? Where XXXXX is encrypted value of the Client CPU Serial Number, Im developing a program which will be highly targeted to be cracked, currently Im making HW fingerprint comparison inside my code twice, once when running and once when executing the same function which will be like this ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |