.NET Advanced Protection Parameters
The table below describes the advanced protection parameters available in Sentinel LDK Envelope for .NET assemblies. Default values are provided where relevant.
|
Parameter Name |
Description |
|---|---|
|
LOCKING_TYPE |
Determines the type of Sentinel protection key to which the program can be locked. |
|
BACKGROUND_CHECK_AUTO_RELOGIN |
If the Sentinel protection key periodic background checks fails to detect a Sentinel protection key, the program attempts to log in to the key a second time before the user is informed that the key is missing. |
| Strong Name Key File |
Select the check box and select a strong name key file if you want to sign the .NET assembly automatically following Sentinel LDK protection. This option is not available when the mixed mode or the Only Windows shell protection type is selected. For more information, see .NET Considerations. |
|
If selected: >Envelope displays a field that you can use to specify XML parameters for a custom login scope. >The protected program will only search for a Sentinel protection key according to the custom login scope that you specify. For information on the syntax for login scope parameters, see the topic "Scope Input XML Tags" in Sentinel Licensing API Reference. You can also paste a login scope that was created using Sentinel LDK ToolBox in this field. |
The list of parameters available varies according to the protection type selected on the General tab.
The following additional parameters appear when the protection type is set to Only Windows shell or Method level & Windows shell:
|
Parameter Name |
Description |
|---|---|
| CHECK_SYSTEM_DEBUGGER |
When set to True, the protected program is configured to counter system debugging. Set this parameter to False only when the protected program is run in a development environment. |
| CHECK_USER_DEBUGGER |
When set to True, enables debugger detection. Note: If certain applications are running, (for example, Visual Studio), they will be detected as a debugger when this parameter is set to True. As a result, the protected program will not launch. |
| PROTECTION_SEED |
If set to 0, Envelope uses a random seed when protecting an application. If set to any other value, Envelope uses the specified value as the seed. This ensures that each time that Envelope protects a given application using the same parameters, the generated binary will be identical. |
| KEEP_DEBUG_INFO |
When set to True, debug information for the assembly is retained. If the protected assembly will execute in a production environment, this parameter should be set to False for highest security. However, if the assembly is collecting crash dump information, this parameter should be enabled so that crash dump data can be collected. |
Related Topics
Modifying Advanced Protection Details