How to Get Started
To start protecting Linux applications with Sentinel LDK, set up your work environment as described in this section.
Perform on a Windows machine:
>Set up Sentinel EMS or Sentinel LDK-EMS. Set up Sentinel Vendor Suite. (For details, see the
Perform these steps on a Linux Intel machine:
The steps that follow must be performed on a Linux Intel machine, regardless of whether the protected application will run on a Linux Intel platform or a Linux ARM platform.
1.Do one of the following to set up your protection environment:
•Copy and unpack the following package from the machine where Sentinel LDK is installed to your Linux machine:
%ProgramFiles(x86)%\Thales\Sentinel LDK\Additional Platforms\Linux\Sentinel-LDK.tar.gz
OR
•Download and unpack the Sentinel LDK Linux package (Sentinel-LDK.tar.gz) from Thales to your Linux machine. The download information is provided in the
The following directories are included under Linux:
•API: Contains the Sentinel Licensing (Run-time) C, C++, and Java API files. For C, both Linux Intel and Linux ARM libraries are provided.
•Docs: Contains Sentinel LDK documentation
•Redistribute: Contains the firmware update V2C and the Sentinel LDK Run-time installers
•Samples: Contains the following:
–C, C++, and Java samples for the Licensing (Run-time) API. For GCC, both Linux Intel and Linux ARM samples are provided.
–Activation Demo
•VendorCodes: Contains the demoma.hvc Vendor Code
•VendorTools: Contains the following tools:
–Sentinel LDK Master wizard ( in the VendorSuite subdirectory)
–Sentinel LDK Envelope (in the Envelope subdirectory)
–Sentinel LDK dfcrypt utility (in the Envelope subdirectory)
2.Install the Sentinel LDK Run-time Environment (included under Linux/Redistribute/Runtime) on your Linux machine. For more information, see the
NOTE Always ensure that the most recent Run-Time Environment is installed on both the vendor's machine and on customers' machines. This is especially important for Sentinel LDK versions 7.9 and later.
3.Sentinel Vendor keys (Sentinel Master key and Sentinel Developer key) are provided in the Sentinel LDK Starter kit. A separate set of Sentinel Vendor keys is provided for each Batch Code. The Batch Code is printed on each Sentinel Developer key and on all of your Sentinel HL keys. (The Batch Code is a representation of your confidential Vendor Code.)
If you have one or more Sentinel Vendor keys, use the Sentinel Master Wizard to introduce one Vendor key for each Batch Code on the Linux machine and generate the Sentinel Licensing API for Linux as follows:
a.Connect the Vendor key to your Linux machine.
b.You may need to set the executable flag for masterhasp (located at /Linux/VendorTools/VendorSuite) with the following command: chmod a+x masterhasp
c.Run /Linux/VendorTools/VendorSuite/masterhasp.
NOTE masterhasp is a GUI application that requires root privileges. On some installations, it may be necessary to add root to the local X server access list in order to launch masterhasp. This can typically be done using the following commands:
xhost local:root
sudo DISPLAY=:0 ./masterhasp
d.The Master Wizard detects the new key. Follow the remaining instructions in the wizard to introduce the key to Sentinel LDK.
–Your customized Sentinel Licensing APIs are stored under:
/root/Documents/Thales/Sentinel LDK 10.0/API/Licensing/C
–Your vendor-specific library (haspvlib_vendorID.* file) is stored in the directory:
/var/hasplm
–Your Vendor Code is stored under:
/root/Documents/Thales/Sentinel LDK 10.0/VendorCodes
The name of the file is [batchCode].hvc. For example, if your Batch Code is W3FLY, the file name will be W3FLY.hvc.
NOTE To generate customized RTE installers for Linux, use the Windows version of the Master Wizard. For details, see