Resolved Issues
>Service Pack: 8.3.101 | January 2022
>Service Pack: 8.3.100 | December 2021
>Service Pack: 8.3.002 | December 2021
>Service Pack: 8.3.001 | November 2021
>Patch: 7/2021: Sentinel LDK-EMS and Vendor Suite (KB0024494) | July 2021
The following issues that were reported by vendors are resolved in this release of Sentinel LDK.
Service Pack: 8.3.101 | January 2022
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-114671 |
After installing the Sentinel LDK 8.3.100 service pack, Envelope would fail when the following conditions existed: >You are applying protection using the Java, .NET, or Windows V3 protection engine. >The Developer key is attached to machine where Envelope runs. The following message would be displayed: No appropriate key( Master/Developer key or protection key with the required Feature) was found (7). The same problem would occur when using envelope.com. The problem would not occur when the Master key was connected to the machine. |
Sentinel LDK Envelope |
Service Pack: 8.3.100 | December 2021
Service Pack: 8.3.002 | December 2021
The following issues that were reported are resolved in this release of Sentinel LDK.
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-113197 |
CVE-2021-44228 is a remote code execution vulnerability in Apache Log4j 2.12.0. This vulnerability is remotely exploitable without authentication. It can be exploited over a network without the use of a username and password. The Apache Log4j module is used by Sentinel LDK in Sentinel LDK-EMS and in the Sentinel LDK Activation sample for Java. (As a client-side application, the Activation sample for Java is not affected by this vulnerability.) This service pack upgrades the Apache Log4j module to version 2.15.0, which resolves the vulnerability. Note that this is a critical vulnerability that must be patched using Sentinel LDK Service Pack 8.3.002 or later. For more information regarding this and any older security issues, see: https://cpl.thalesgroup.com/software-monetization/security-updates |
Sentinel LDK-EMS, Sentinel LDK samples |
Service Pack: 8.3.001 | November 2021
The following issues that were reported by vendors are resolved in this release of Sentinel LDK.
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-111464 |
See Issue with Vendor-Specific APIs and the Vendor Library 8.31 has Been Resolved |
Vendor-specific Licensing API DLLs |
| SM-111405 | After copying an entitlement, it was not possible to edit the Feature details in the entitlement. | Sentinel LDK-EMS |
| SM-111803 |
For an application protected using: >Java Class-Level protection >the V3 Engine >SL UserMode locking type The application could not be accessed unless hasp_rt.exe is present. The error "No matching Feature found (E0050)" was displayed. |
Sentinel LDK Envelope |
Release: 8.3 | October 2021
The following issues that were reported by vendors were resolved in the Sentinel LDK 8.3 release.
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-84417 | Documentation regarding extending a time-period-based license has been clarified. Documentation now states that a license with an Expiration Date license type can be extended. The expiration date for a license with the Time Period license type cannot be modified. For details, see the Sentinel LDK Software Protection and Licensing Guide. | Documentation |
| SM-103456 | When available activations were increased by editing the Product key, Sentinel LDK-EMS also increased the value of Previous Activations by the same amount. As a result, Remaining Activations would remain 0. | LDK-EMS |
| SM-108144 | Under certain circumstances, when more than 15 dynamic memory files were defined, it was not possible to add more dynamic memory files when creating product. | LDK-EMS |
| SM-106179 |
When generating a license that contains dynamic memory files with maximum size 65,535, an error would be returned. |
License Generation API |
| SM-105804 | When deploying licenses on an Android device, an error message similar to the following was sometimes returned: "Could not generate the license because: The host machine fingerprint is invalid." | Licensing API |
Patch: 7/2021: Sentinel LDK-EMS and Vendor Suite (KB0024494) | July 2021
The following issues that were reported by vendors were resolved in Sentinel LDK Patch 7/2021: EMS and Vendor Suite (KB0024494).
| Reference | Resolved Issue | Components |
|---|---|---|
| SM-101263 | Documentation for Java exception handling and class-level protection has been improved. | Documentation |
| SM-102028 | The documentation for Sentinel Licensing API (for C and for Java) has been corrected as follows: The return status HASP_INV_ACTION (59) has been changed to to HASP_INV_DETACH_ACTION (59). | Documentation |
| SM-102724 | The description of "Specifying an HTTPS Certificate – XML Scope" in Admin API documentation now indicates that the certificate referred to is a public certificate. | Documentation |
| SM-99967 | In Sentinel EMS 8.2, copying an existing entitlement of type "Protection Key Updates" would generate the error: "An internal error occurred. Contact the system administrator for assistance." | Sentinel LDK-EMS |
| SM-101036 | Fixed an issue that prevented the smooth upgrade of HL keys from HASP configuration to Driverless configuration. | Sentinel LDK-EMS |
| SM-101439 | After upgrading Sentinel EMS from 8.0 to 8.2, it was not possible to use the EMS Web Services PUT request to create new entitlements. | Sentinel LDK-EMS |
| SM-99684 | In a virtual machine, certain protected applications would repeatedly start child processes at startup until the CPU was 100% occupied. The application would fail with: "Internal error 0x7103 occurred!" | Envelope |
| SM-100285 | An application that was protected with a patched version of Envelope for Mac would fail at seemingly random intervals due to an EXC_BAD_ACCESS exception. | Envelope |
| SM-101818 | Envelope would fail when a .NET DLL file was added to the project. | Envelope |
| SM-103047 | A protected Unity 3D application would fail when loading the RenderDoc pluglin. | Envelope |