It is bad technology when user will type the name and serial number and after that you will run own algorithm for calculation of serial from user name for next compare. Better to generate a few Kb of key don't forget to send instruction about key entering than use a key-generator for 10 characters with standard literal symbols. Of course, it depends from crypt algorithm but your key must be long. If cracker will use a brute force cracking, this task will take a lot of additional time and in pair with good encrypt method the task of cracking will be unreal. To trace all code of program or spend a lot of time on your program is hard task for any cracker. You can check a different part of serial number in other days of month or better to activate this validation after few days after first validation receipt. If cracker will find a validation procedure then he'll find an one part of validation only. It allows validating your code in few procedures. I mean that you can generate an activation code using two-three-: algorithms.
Save this information somewhere and show it later better after few days. Change a F2CA name and don't forget about rule 1. If cracker will disable this procedure, you program will not work correctly. Always place the checking code in some important procedure that is required for your program. Use a different methods of code checking - checksums, own labels.
It will increase time of cracking because cracker must found a gold mine in the rubbish. Also don't forget that additionally you can creat e the some own hidden file during installation and use a date-time of this file. Better to use a date-time of some system files SYSTEM.
0 kommentar(er)
