I used an amateur license key scheme in xplorer² it took a couple of years before the first keygens appeared back in 2006(?). People who get hold of these keygens can offer themselves free license keys for your software and your business is losing money. The worst case scenario for your licensing is your key generator scheme being discovered by some mad dog pirate, who then goes on to distribute keygens. Finally from what I could tell, these licensing tools do not support secure public/private key RSA algorithms (or their customer support wasn't tech savvy), so you risk being keygenned. Why reinvent the wheel? Believe it or not sometimes off the shelf protection solutions are easier to crack because so many programs use them, there are automated tools to strip their protection! They also use some obscure tricks to protect the software from debuggers and other tools used by the pirates, which may cause antivirus programs to mistake your software for a virus. WinLicense, Armadillo etc), or you can roll out your own key generator like I did with xplorer².
There are products you can buy to add protection and licensing to your code (e.g. It is a separate skill especially when considered as part of the total protection against piracy, reverse engineering etc.
Generating keys isn't easy for the average windows programmer.
0 kommentar(er)
