Windows (V3 Engine) Default Protection Settings Screen
Protection settings for Windows programs (with Windows V3 engine) are displayed when you select Windows V3 under Default Protection Settings in the Project pane. All the settings can be modified.
The Windows (V3 Engine) Default Protection Settings screen contains the following settings:
|
Set a time interval (in seconds) for periodic background checks for a Sentinel protection key with the required licenses. Regardless of the setting for this field, the License Manager checks for the required license when the application is started. If the License Manager detects that the protection key is missing when a background check is performed, a notification is displayed. The user can click the OK button to dismiss the message box and to check again for the protection key. For more information, see Periodic Background Check Behavior. Periodic background checks does not work if you use Envelope to protect a DLL for a Windows console application, because console applications do not have a windows timer. IMPORTANT For applications that may use the Execution Count license type and the Admin License Manager: End users can configure the Admin License Manager session to time out after as little as 10 minutes of inactivity. If the background check interval is greater than the idle time-out interval and a time-out occurs, the background thread will re-login to the protection key. This could result in additional consumption of licenses for applications licensed with the Execution Count license type. Therefore, Thales recommends that you do one of the following: >Set a time interval of less than 10 minutes for Periodic background checks in order to prevent the session from timing out. >Take other precautions to ensure that the end user does not set the idle time-out interval to a value lower than or equal to the Periodic background checks interval. |
|
|
User debugger detection |
Enables/disables debugger detection. NOTE If certain applications are running (typically, developer tools), they will be detected as a debugger when this setting is enabled. This means that the protected program will not launch. |
| Disable key for attempted tampering |
If selected, the Envelope run-time module in the application disables 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 fail or will display an error message and stop executing, depending on the type of tampering detected. Only relevant when the application is licensed with one of the following: > A Sentinel HL (Driverless configuration) key NOTE 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. >A Sentinel CL key (an SL key that is enabled for cloud licensing) NOTE You must connect a Sentinel Developer key or Master key at the time that you protect the application. Tamper detection functionality is not supported for the DEMOMA Batch Code. For details, see Enhanced Protection Against Tampering for Sentinel Keys. |