- Go play along license key how to#
- Go play along license key activation code#
- Go play along license key activation key#
- Go play along license key free#
What about virtual machines? It's probably feasible to detect all currently existing virtual machine configuration, at the risk of a few false positives now and then.
Go play along license key free#
That means any user can get a free licenses from time to time by pretexting a hardware failure. And I'm not inviting you to check that my hardware has failed, so you'll have to take my word for it. You'd better respond fast, because if your application is important I want to minimize downtime.
my hard disk breaks)? I'm certainly not going to purchase your application if I can't go on using it after a hardware problem, so at a minimum you must be prepared to handle key change requests. You propose to use a hardware signature as part of each user's unique key. Apparently, you want to ensure that for each purchase of your application, there will only ever be one computer on which the application is installed and runnable. to be sure the user can not use the same regcode+activationcode.įirst, you should make it clear what you're trying to protect. Hardware spoofing, Revoking license keys i.e. What I am looking for is good/feasible solutions to the 2 points.
Go play along license key activation key#
The application does not call out regularly, if a network connection is available the user gets the option to make a more automatic registration, otherwise he/she gets a registration key, enters it in the software and gets an installation ID which is provided to me, registration code + installation ID generates an activation key that the user gets from me which then unlocks the software. But I could modify the hardware-key scheme to take into account and allow for some changes.Īlso because of this the software will most likely not be run inside a VM, good point though and I haven't thought about that. I currently have a scheme that works, I should mention that the most common product is installed in an embedded enviroment where hardware-changes are very rare and if there is a hardware failure then most certain the machine is broken. One idea I had was to add some random data to the "unique" key, this random data would be stored in an obscure way, if the user deinstalls the application this random data would be removed, and some kind of hash with the previous random data and the license data would be generated which could be sent to me to verify that he really have uninstalled the application and made me sure that he wont be able to use the previous license data again since the random data had changed.
Go play along license key how to#
If the user decides to uninstall the application and wants to move it to another computer, there is nothing that prevents him from using the old license data again at the old computer and still obtaining new license data for the new installation.ĭo you have any suggestions on how to resolve these issues?.to produce the same "unique" key on another computer he could use the same license data. If the user manages to spoof hardware signature etc.however this scheme lacks two properties: This is fair and quite simple to implement, one can choose different crypto algorithms etc.
Go play along license key activation code#
When the application runs it validates the activation code by comparing the "unique" key and a datablob received by decrypting the activation code. The user sends this key and a registration code when he wants to register the software and receives an activation code. I am working on a software which I would like to protect using some kind of licensing scheme.Ī basic scheme would be to generate some "unique" key for a user. This is my first question so please be gentle.
0 kommentar(er)
