Optional Protection Options: Basic

The table below describes the basic protection options that you can set while protecting your application using Sentinel RMS Envelope:

Option Description Default Setting
-b: --bgchk:<time>

Enables you to specify the time interval for performing background checks. The protected application checks for the presence of a valid license after the specified time interval.

If the background check value is greater than the key lifetime value of the license, the license check will be done according to the key lifetime value.
The allowed values are:

>0 = Background checks disabled. In this case:

The license is released immediately after launching the application.

The license is not required for continuous use of the protected application.

> Integers = Time intervals (in seconds) for background checks.

Use of this option is recommended to periodically check that the licensing session is alive and is not bypassed at any point during the protected application execution.

Default: 300 seconds.

-cs: --csrv:<contact server>

Sets the Sentinel RMS License Manager.

Notes

>For network licensing, specify the hostname or IP address of the machine where the Sentinel RMS License Manager is installed.

>For standalone licensing, set NO-NET as the value of this option.

>Alternatively, the Sentinel RMS License Manager name can be set using the LSHOST or the LSFORCEHOST environment variables.

If no Sentinel RMS License Manager is set, the application looks for the license first on the local computer, and then it will make a broadcast for a license, looking for License Managers in the subnet.
--eval

Protects the application in This mode. The Sentinel LDK Developer key is not required for protecting applications in evaluation mode

>If this option is used, the application will be protected in evaluation mode only, even if the Sentinel LDK Developer key is available.

>In this mode, the protected application can be used for a period of up to 30 days, starting from the day it is protected.

>For more information, refer to the Using Sentinel RMS Envelope in Evaluation Mode section.

-
-f: --fname: <feature name>

Sets the feature name, a mandatory option.

A feature identifies a suite of application, an application, a file, or a functionality of the software that needs to be licensed. The feature name can consist of alphanumeric characters, without spaces (in the ASCII range of 32-127).

>The maximum length of the feature name is 24 characters.

>The specified feature name should match the feature name that was specified in the license at the time of license generation.


-
-h --help

Displays user help.

-
-lib:<library absolute path>

Sets the absolute path pointing to the Sentinel RMS licensing library. A mandatory option.

>To protect a 32-bit/64-bit application/DLL, provide the path of the 32-bit/64-bit library.

-
--msg-out:<mode>

Sets how the run-time user messages are displayed. Possible values are:

>1 - Windows: Displays messages in a message box on Windows.

>2 - Eventlog: Logs all the events related to the execution of the protected application in the Windows Administration Tools Event Viewer.

>4 - Stderr: Logs all the errors encountered during the execution of the command-line-protected applications in standard error (stderr). This functionality is not available for GUI-based Windows applications.

>You can also specify a combination of the available values (using the OR operator).

1
-S1:<secret>...-S7:<secret>

Sets secret strings for the challenge-response mechanism.

The challenge-response mechanism is a technique used for authenticating the Sentinel RMS License Manager. The challenge strings (secrets) you define are encrypted within the license, with only the RMS License Manager knowing how to decrypt them.

The RMS License Manager associates a secret with a feature, provided by the license code. The application also contains this secret.

During the RMS License Manager validation process, the protected application sends a “challenge” to the RMS License Manager with a data string. The RMS License Manager computes a response based on to the arranged algorithm, the values, the data string, and the secret, which it to the protected application. The protected application computes the expected response locally using data string and the secret, and verifies that the expected response matches the response returned by the RMS License Manager.

Notes

>You can define up to 7 secrets
(1 to 7) for the challenge-response mechanism.

>Each secret can contain up to 12 printable characters.

>The secrets specified here should match the secrets defined in the license.

>If the license contains multiple secrets, you can specify fewer secrets in an exact sequence. For example, If the license contains 7 secrets (S1...S7), you can choose to specify only 3 of the secrets (S1, S2, and S3).

Disabled.
-t: --enable-ts:<val>

Enables the protected application to run on a Terminal Server/ Remote Desktop.
The available options are: 

>0 - Disable server(TS), Disable RDP

>1 - Disable server(TS), Enable RDP

>2 - Enable server(TS), Enable RDP

1
-v: --ver:<feature ver>

Sets the feature version. Mandatory if a version is specified in the license.

The maximum length of the version is 11 characters.

>The specified feature version should match the feature version specified in the license.

>Do not use this option if the license does not contain a feature version.

-