We are happy to announce the availability of Sentinel LDK and Sentinel HASP Run-time Environment Installer 7.65 for Windows, Linux and Mac.

Please refer to the readme included in the packages available at SCC for supported operating systems, enhancements, known compatibility issue, and issues resolved.

We are happy to announce the availability of Sentinel LDK and Sentinel HASP Run-time Environment Installer 7.63 for Windows, Linux and Mac.

Please refer to the readme included in the packages available at SCC for supported operating systems, enhancements, known compatibility issue, and issues resolved.

We can set exact expiration time for a product to be detached using hasp_transfer() licensing API by specifying the detach duration for the product between the <duration> </duration> xml tag for a specified product id.

However, the exact expiration time for a license can’t be specified in the ACC (it’s just the expiration date that can be specified) therefore, for now detached license expires at midnight of local time when detached via ACC.

We are happy to announce the availability of Sentinel LDK and Sentinel HASP Run-time Environment Installer 7.61 for Windows and Linux.

Please refer to the readme included in the packages available at SCC to see the supported operating systems, enhancements, known issues and issues resolved.

Gemalto/SafeNet has identified some vulnerabilities with the use of Sentinel LDK EMS server and License Manager services that may impact the confidentiality and integrity of the services if exploited.

Customers using these services are advised to follow the mitigation guidelines outlined in security bulletins at the following links:

• https://sentinel.gemalto.com/technical-support/security-updates-sm/
• https://supportportal.gemalto.com/csm/?id=csm_product&sys_id=50303b92db852e00d298728dae96199d&table=sn_customerservice_product_name

Note: This section is restricted, customers need to login before accessing the proper content of each security bulletin.

Error when trying to install the RTE on windows machine:

 Unable to install c:\WINDOWS\system32\setup\aladdin\hasphl\akshasp.inf file.

This is an internal error. For assistance, contact your administrator or the software manufacturer.

Status Code: 42 5 1340

Resolution:

 1. Restart your computer into safe mode.

 2. Login using the Administrator’s account

 3. In Start, Accessories, right click on Command Prompt, and click on Run as Administrator.

 4. In DOS type :-  net stop cryptsvc.

 5. Press enter and wait for the computer to say it has stopped this service

 6. Close DOS and remain in Windows Safe Mode.

 7. Go into My computer and navigate to your Windows directory.

 8. Find the folder windows\software distribution and remove the contents, but not the folder itself.

 9. Then navigate to windows\system32\catroot2 folder and remove the contents of that folder.

 10. Right click on the catroot2 folder and rename it to catroot3.

 11. Restart windows and login as normal.

What is a Windows 10 “big update”?

Starting with Windows 10, Microsoft has changed the manner in which they manage the release of the Windows OS.

Once Windows OS was a software product. Microsoft delivered various versions (Windows 98, NT, XP, and so on) and provided service packs or small patches for each of them.

Windows 10 is different. Windows 10 is not a software product but a service. Instead of releasing a new OS, Microsoft has been releasing new features to Windows 10 as a “big update” (or “big patch”).

[Windows 10 major big update]

Build 1607 | 2016 September | Anniversary Update

Build 1703 | 2017 April | Creators Update

Build 1709 | 2017 October | Creators Update Fall

How is a Windows 10 big update distributed online?

Big updates are distributed in three ways:

1. Microsoft Site. After the official release date, you can find a link to get the big patch on the Microsoft Windows 10 official product site.
2. Microsoft Distribution Plan. Windows Update users cannot obtain a big patch by request – they are dependent on Microsoft's distribution plan.  Microsoft distributes the big patch as a Windows Update, but it is usually delivered 2-3 months after the official big patch release date. This is because Microsoft needs time to fix issues that are typically discovered by early installation from the Microsoft site.
3. Insider Preview Program. Windows 10 users can get the latest big update before the official release via the Insider Preview Program, but these releases are categorized as "Preview Builds" and are not stable. Sentinel LDK does not support preview builds.

Possible issues faced after Windows upgrade:

1) Sentinel LDK License Manager service no longer available

After the installation of a big update, you might see "Sentinel LDK License Manager" service installed but stopped.

Resolution: Manually start the service from the Computer Management – “Services and Applications” panel.

2) SL-AdminMode license disappeared

If you have upgraded your system to the latest build right after the release date, you might note that your existing SL-AdminMode license has been removed and is no longer visible in the Admin Control Center on the page at http://localhost:1947/_int_/devices.html.

Resolution: Make sure License Manager is active (as described in issue 1). If the Sentinel LDK License Manager service is not present, install the Run-Time package again from one of the following links:

Sentinel HASP/LDK - Windows GUI Run-time Installer

https://sentinelcustomer.gemalto.com/DownloadNotice.aspx?dID=8589947119

Sentinel HASP/LDK - Command Line Run-time Installer

https://sentinelcustomer.gemalto.com/Download Notice.aspx?dID=8589947873

Your SL-AdminMode license will then be active again.

In case your Windows 10 OS was updated through an automatic Windows Update, your existing SL-AdminMode license should not be affected.

The issue does not affect SL-UserMode licenses or Sentinel HL USB dongles.

For any additional issues, please contact your Software Vendor. 

We are happy to announce the availability of Sentinel LDK and Sentinel HASP Run-time Environment Installer 7.60 for Windows, Linux and Mac.

Please refer to the readme included in the packages available at SCC to see the supported operating systems, enhancements, known compatibility issue, and issues resolved.

Recently we published RTE 7.54 on Windows Updates.

Few customers reported the following small issue when doing the upgrade (we had RTE 7.41 before and now RTE 7.54).

Issue: During the upgrade, haspdlock.sys driver might not be properly updated.

As a consequence, HASP4 protected application (which still relies on hardlock.sys to access the legacy dongle) fails to find the dongle.

We can quickly confirm it by running cmd-line command which shows hardlock.sys not running:

Solution: Reboot the machine. Or try first to restart hardlock.sys via CMD Prompt with Admin permissions:

We suspect that the reason for this is OS delays the stop of the old hardlock driver, and thus the start does not occur.

Below are the highlights:

• It is supported/possible to sign the Vendor DLL (by customer at their end) which is available at "C:\Program Files (x86)\SafeNet Sentinel\Sentinel EMS\EMSServer\webapps\ems\haspTools”
• Customer can also sign the generated RTE installer.
• We are though planning to provide signed VLIB (no tentative schedule as of now) . However, customer needs to sign generated RTE installer by themselves (as it is created at their end).