Enhanced Protection Against Tampering for Sentinel Keys
A native Windows or .NET application that is protected with Sentinel LDK Envelope can provide protection against tampering when licensed with one of the following keys:
>Sentinel HL (Driverless configuration) key with firmware version 4.54 or later.
>Sentinel CL key (Sentinel LDK Run-time Environment 8.51 or later is required on the user's machine)
The Envelope run-time module in the application can disable the key if the module determines that the user has attempted to tamper with the key or with the protected application. Once the key is disabled, the protected application will no longer execute. The application will fail or will display an error message, depending on the type of tampering detected.
If the customer's HL key has a Firmware version earlier than 4.54, key disabling is not supported. If tampering is detected, the protected application will fail or will continue to operate, depending on the type of tampering detected. In either case, the customer can continue to use the application afterward.
In Sentinel LDK Envelope, you can enable tamper detection functionality for a protected application by selecting the check box for Disable key for attempted tampering in the Protection Settings screen. By default, this check box is clear.
The "disabled" state of a key can be determined at the customer site by the get_info() function in Sentinel Licensing API and can be viewed in Sentinel Admin Control Center.
The "disabled" state of a key does not affect your ability to send license updates to the key. Any updates that were applied to the key before or after the key was disabled will be in force if you re-enable the key.
You have the option to re-enable a disabled HL or CL key. For more information, see the