Resolved Issues

Given the following circumstances:

1.Sentinel LDK-EMS is configured to include the customer name in the License File Name Format parameter.

2.A customer is defined in Sentinel LDK-EMS with non-Unicode characters in the customer name.

3.An entitlement is generated for the customer, and the license is activated.

4.The generated V2C or V2CP file is downloaded.

The generated file was named "downloadV2CFile.html" instead of containing the relevant customer name.

In Sentinel LDK-EMS 9.0, the Map button (under the Product Catalog page) for protection key memory was no longer accessible for products that were deployed under earlier versions of Sentinel LDK-EMS.

Under certain circumstances, attempting to check in a C2V file would result in the error Unable to find Vendor with ID {0}. 

Under certain circumstances, clicking Produce for an entitlement that had already been produced and then returned to the Draft status would result in an internal error.

When Envelope is used to protect a python application that utilizes multiprocessing, under certain circumstances a STATUS_SHARING_VIOLATION error would occur.

Envelope would fail while attempting to protect an application with a large number of PE import entries.

The Generate License popup was not displayed when a user clicked the Offline Activation button in the Customer Portal.

SM-145697

When adding products to an existing entitlement, the Product Selection list would include products that were already included in the entitlement.

The LMS would fail when installing a license if the following conditions exist:

>The V2C file contains customer info and readable=no.

>The fingerprint for the license was generated with an RTE version earlier than 8.5.

An unhandled exception could not be detected by native code when a .NET application protected by WinShell.

Envelope .NET runtime signature check would fail on CentOS Stream 9.

Need more condition check for Electron application.

When introducing a Master (USB) key in Master Wizard, the folder name had been changed from Runtime to Licensing. but the required corresponding change had not been implemented in Envelope for copying the Linux/ARM libhasp*.so files to the output folder.

The error "double free or corruption" would occur when exiting a class level-protected jar.

Advanced debugger detection did not work correctly for certain DLLs.

.NET Envelope runtime now supports dynamic GUI behavior. Error output of a .NET Envelope protected application now only outputs the error in the GUI when a GUI is available. If no GUI is supported, messages are automatically recorded in a console/eventlog.

Resolved an issue with a manually-changed Envelope project file with AppOnChip enabled. Loading this special Envelope project file and re-enabling AppOnChip would sometimes cause the Envelope GUI to fail.

Under certain circumstances, UDP packets may be lost. Broadcast search now repeats the UDP transmission multiple times to overcome the loss of UDP packets.

The License Manager was not able to keep track of more than 2,000 clients' LM identifiers. This could result in incomplete information when listing detached licenses in the server Admin Control Center pages.

The limitation of 2,000 LM identifiers has been removed.

An issue which could lead to an application freeze after Envelope protection has been resolved. This issue would occur due to a deadlock when calling memcpy() in a secondary thread while loading the engine via dlopen().

An issue with "large address" awareness of the Envelope command line application has been resolved. This issue would occur under very specific circumstances if the address space is already largely packed.

Previously, when a proxy was configured in ACC, the LM would attempt to resolve DNS names, even if they were not resolvable in the local network. This resulted in connection failures. Now, when a proxy is defined in ACC, the LM no longer attempts to resolve DNS names. Instead, it allows the proxy to handle DNS resolution.

Under certain circumstances, licenses protected with the FQDN clone protection scheme were marked as cloned after updating the vendor library (vlib) to version 9.12 or 9.13. This issue is resolved after upgrading to vlib 9.15 or later.

Sentinel Admin API was not able to retrieve client identity information when the client identity was defined with multiple key IDs and admin_get was called using a specific key ID in the scope.

If the session username contains the "&" character, the GetInfo function would report the value in the XML structure as specified, resulting in an invalid XML file. For example:

<session username="AB&C" />

Now, the character is reported back as an XML entity. For example:

<session username="ABamp;C" />

Support of asynchronous I/O in the file copy function of Windows update KB5022913 has been added.