Hi,
I hope you understand what Node-Locked licensing means:
- How are we supposed to handle different users and license activations. Why cryptlex allows activation with the same key for different users from same machine. how can we prevent that. If we check if the key is activated already in different user it shows as not activated and allows activation again. Can we restrict the trial as one activation per machine regardless of users? is that possible? Can you explain why it allows like this?
Cryptlex identifies a machine by it’s hardware fingerprint, which has nothing to do with the Linux Distro or current user, even if user installs some other Linux Distro or logs in as another user, the machine fingerprint won’t change. That’s why different users on the same machine can activate your software with the same key. A key is bound to the machine and not the user.
Restricting trial to one user is of no use as once the verified trial expires, it will expire for all the users simultaneously, even if your customer reinstalls the OS it will still show expired.
Restricting key to one user can be done in a following manner:
1- Create a custom_license field named “linux_user”, which your customer needs to provide at the time of key generation, later on it can be used to verify the current user on the system, if it does not match you can prevent the user from using your software.
- we give new versions of our product as tar file periodically to our customers. In that case, how do the activations work? As we tested, it shows as license activated without moving any prodcut.dat files from prev ones. how does that work? are you storing any information in the system?
Yes, the data is stored locally in the current user folder, as well as on our server. If a local copy is found, it’s digital signature is verified and used otherwise you need to activate again. Product.dat file is not used for storage, it is a read only file which contains the license data.
