Machine-locked
| Sentinel LDK Functionality | Creates an activation key that is locked to a specific machine |
| Software Distribution Method |
>Physical package >Electronic distribution |
| Applicable Key Types |
>All Sentinel HL keys except Sentinel HL Basic >Sentinel SL (including CL) |
| Protection Method |
>Envelope-based automatic implementation >API-based automatic implementation |
Description
The license can only be used on the machine on which it was installed. A machine-locked license can be combined with any of the licensing models in this guide.
Implementation 1—Locking to a Sentinel SL key
This model is applicable when a Sentinel SL key provides sufficient security for your needs.
1.Select and implement the required licensing models.
2.Distribute your software using a Sentinel SL key. Sentinel SL keys are always locked to a specific machine.
Implementation 2—Combined locking to both a Sentinel SL key and a Sentinel HL key
This model is applicable when you want to lock your software to a Sentinel HL key for enhanced security, and also wants to use a Sentinel SL key to lock your software to a specific machine. The Sentinel SL key will require remote activation.
1.Select the executable file that you want to license, and determine two Feature IDs by which it will be identified. One Feature ID will be used to lock the license to the Sentinel HL key, and the other to lock the license to the Sentinel SL key and the machine.
2.Select your protection method:
•For combined Envelope-based and API-based automatic implementation
Protect the executable file using Sentinel LDK Envelope , specifying one of the Feature IDs. In your code, insert a Sentinel Licensing API Login call to other Feature ID.
•For API-based automatic implementation
In your code, insert Sentinel Licensing API Login calls to both Feature IDs.
3.In Sentinel LDK-EMS, create two Products, one for each Feature ID. Define the license terms for both Products—for example, an execution-based license or a time-limited license.
4.Burn a Sentinel HL key for one of the Products and
5.Distribute your software with both Sentinel protection keys.
Implementation 3—Locking to a Sentinel HL key
This model is applicable when you want to lock the license to both a machine and a Sentinel HL key—but for security reasons, the end user will not be able to activate a Sentinel SL key online.
This implementation requires a utility to be written that will collect the required identifiers from the machine before or during installation of your software, and subsequently every time your software is run. The initial identifiers are saved in the read-only memory of the protection key, and the run-time identifiers are written to the read/write memory on the Sentinel HL key and validated against the initial identifiers.
NOTE It is recommended that you contact Thales Sentinel Professional Services for a detailed implementation plan.