![]() ![]() Digitally signing your code won't help, they can remove that signature, or resign it. Same applies even if you supply a dongle - if someone wants to, they can patch out the check for that too. Even if they can't someone will, and will distribute the hacked version. It doesn't matter how convoluted you make your scheme, anything you do for this will ultimately be security through obscurity and they will always be able to this. Or, they will work out a key that passes all checks and distribute that, or backdate the clock, etc. ![]() One way to distribute the license file (on windows) is to provide it as a file which updates the registry (saves the user having to type it).īeware of false sense of security though - sooner or later someone will simply patch your program to skip that check, and distribute the patched version. Then you just verify it within your program. Then encrypt that using some crypto algorithm with a fixed key or hash it. program features to enable, expiry date, name of the user (if you want to bind it to a user). This could include anything you want - e.g. You can do something like create a record which contains the data you want to authenticate to the application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |