I'm not a programmer, but I think that the keygens situation could be solved simply by not providing the ability to register, a fully functional (if the developer wants to), trial version.Dark Wizard wrote:Unfortunately for nikkos, xplorer2 184.108.40.206 (back in 2011) and 220.127.116.11 already have "keygens" available on torrent sites.
Since ordering requires an Internet connection, why not send the buyer a unique one-time download link to a setup file for a fully functional pre-registered version instead of an unlocking key?
Of course, that version could be spread on warez sites, but what would prevent anyone to spread a legit license key as it is now?
And if you want to identify the leaked full version, you could have individually signed builds. Each downloaded file has a unique signature which will be assigned to the buyer's ID, so if that customer spreads the full version, it can be easily identified just as it would currently spread a legit license key.
Of course, this is regarding keygens only, not cracks or patchers.
Also, updates should be designed not to interfere with the unique signatures, and they should act like pacthers instead of full installers. They could also be programmed to refuse patching black-listed signatures, by storing them signatures in the updater and checking against the existing signature of the installed application.