Luna HSM Client 10.6.0
Luna HSM Client 10.6.0 was released in August 2023. It includes bug fixes and security updates.
NOTE This version of Luna HSM Client is compatible with Luna HSMs with firmware 6.2.1 and newer. Features that do not have client version dependencies will function without issue.
New Features and Enhancements
Luna HSM Client 10.6.0 includes the following new features and enhancements:
Configurable TLS Ciphers
Customize Luna Network HSM TLS ciphers used by the appliance in:
>NTLS: Network Trust Link Service
>STC: Secure Trusted Channel
>CBS: Call Back Server (Used for audit logs, as well as the PED Client)
Choose from the provided list, to include or exclude appliance-side ciphers. Client and appliance support TLS 1.3.
This feature also requires minimum Luna Network HSM Appliance Software 7.8.3.
Certificate Rotation in HA Mode
Certificate rotation is smoothed and downtime is mitigated. If a new certificate (self-signed or CA-signed for both the client and server certificate on the client) is available for NTLS connection, it is used immediately upon recovery of an HA member, rather than using a cached copy of the outgoing cert, as in previous releases. There is no need to launch a new client instance to invoke a new certificate.
Clusters and Keyrings Enhancements
CAUTION! TECHNICAL PREVIEW -- EVALUATION ENVIRONMENT ONLY
Clusters are presented as a technical preview, to give customers the opportunity to validate our new HSM management features, designed to reduce operation cost and maximize the return on investment of a fleet of HSMs. This release does not provide a migration path from standard Luna partitions or Luna Cloud HSM services to keyrings. Thales recommends Luna Network HSM Appliance Software 7.8.3 with cluster package 1.0.3, Luna HSM Firmware 7.8.2, and Luna HSM Client 10.6.0 to use clusters.
DO NOT INSTALL THE CLUSTER PACKAGE ON A LUNA NETWORK HSM IN PRODUCTION
When the cluster package is installed, access to any existing partitions on the HSM is disabled, and this can only be reversed by re-imaging the Luna Network HSM appliance (see Re-Imaging the Appliance to Baseline Software/Firmware Versions). Re-imaging is a destructive action; all roles, partitions, and keys are destroyed. The Luna Network HSM must be completely reconfigured; all partitions must be recreated and their contents restored from backup. In particular, do not attempt to configure clustering on a Luna Network HSM that already has V1 partitions created; either delete these partitions or re-image the appliance before configuring a cluster.
This release includes the following enhancements to the Clusters feature:
>Expanded PKCS#11 Support on Keyrings
You can install Luna HSM Client 10.6.0 on the following operating systems:
|Operating System||Version||Secure Boot Supported|
|Windows Server Standard||2022||Yes|
|Windows Server Core||2022||Yes|
|Red Hat Enterprise Linux (RHEL)||9.0, 9.1, 9.2 (†)||No|
|Red Hat Universal Base Image (UBI)||8.8||No|
|Red Hat-based Linux (including variants like CentOS and Oracle Enterprise Linux)||
8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6, 8.7 (†)
|SUSE Linux Enterprise Server (minimal client only)||15||No|
* The Linux installer for Luna HSM Client software is compiled as .rpm packages. To install on a Debian-based distribution, such as Ubuntu, alien is used to convert the packages. We used build-essential:
apt-get install build-essential alien
If you are using a Docker container or another such microservice to install the Luna Minimal Client on Ubuntu, and your initial client installation was on another supported Linux distribution as listed above, you do not require alien. Refer to the product documentation for instructions. You might need to account for your particular system and any pre-existing dependencies for your other applications.
† RHEL and CentOS 8.0-9.0 with their original kernels. See also Luna HSM Client 10.6.0.
Supported Cryptographic APIs
Applications can perform cryptographic operations using the following APIs:
>Supported Java versions:
•Open JDK 7 up to Open JDK 21
•Oracle Java 7 up to JDK 21
•IBM Java 7, 8 and 11
This section highlights important issues you should be aware of before deploying Luna HSM Client 10.6.0.
PED-Initiated Remote PED Connection with Self-signed Certificates only
Luna Network HSM Appliance Software 7.8.1 or newer with Luna HSM Client 10.5.1 or newer uses self-signed certificates for PED-initiated Remote PED connections and does not support using 3rd-party (trusted Certificate Authority) certificates for that purpose at this time.
Luna HSM Client 10.5.x on AIX Has Dependencies
Before installing Luna HSM Client 10.5.x for AIX, download and install libgcc10 from the IBM portal:
The LNHClientRegistration script will not work properly with the AIX-standard version of the sed utility. If you will use the LNHClientRegistration script to register your clients, download and install the GNU version of sed.
Backup/USB/PCIe Drivers Not Installed on Windows 10 or Windows Server 2022 Unless Device is Connected
Due to changes in Windows 10 and Server 2022, device drivers are not installed unless the USB or PCIe device is connected to the client workstation. If you plan to use a Luna Backup HSM 7, Luna Backup HSM G5, Luna USB HSM 7, or Luna PCIe HSM with these operating systems, use one of the following workarounds:
>Connect the Luna device to the workstation (or install the Luna PCIe HSM card) before installing the Luna HSM Client software
>After installing the Luna HSM Client software:
a.Connect the Luna device(s) to the workstation (or install the Luna PCIe HSM card)
c.Select the devices you want to install drivers for.
Insecure SSH Ciphers Removed From Luna Network HSM 7.8.0 and Newer
Thales has removed a number of less-secure SSH ciphers from Luna Network HSM Appliance Software 7.8.0. As a consequence, older client versions may not be able to use SSH to access LunaSH. This affects SSH connections, pscp/scp file transfers, plink, and certain procedures that rely on these tools such as the One-Step NTLS Connection Procedure. To avoid connection problems, you must use the versions of pscp and plink from Luna HSM Client 10.4.0 or newer. If you use Linux-standard applications like scp or ssh, ensure that they are updated to the latest version.
The following ciphers have been removed:
Host-Based Accepted Key Types
Host Key Algorithms
Public Key Accepted Key Types
CentOS 8.4 Missing Dependency
Due to a missing dependency on CentOS 8.4 [specifically the symlink (libnsl.so.1) to libnsl was removed], when installing Luna HSM Client 10.5.0 or newer, you must install an additional rpm package first:
Run yum install libnsl before invoking the install.sh script.
CSP/KSP Registrations Can Fail if Windows Update Missing
CSP or KSP registration includes a step that verifies the DLLs are signed by our certificate that chains back to the DigiCert root of trust G4 (in compliance with industry security standards).
This step can fail if your Windows operating system does not have the required certificate. If you have been keeping your Windows OS updated, you should already have that certificate.
If your Luna HSM Client host is connected to the internet, use the following commands to update the certificate manually:
certutil -urlcache -f http://cacerts.digicert.com/DigiCertTrustedRootG4.crt DigiCertTrustedRootG4.crt
certutil -addstore -f root DigiCertTrustedRootG4.crt
To manually update a non-connected host
1. Download the DigiCert Trusted Root G4 ( http://cacerts.digicert.com/DigiCertTrustedRootG4.crt DigiCertTrustedRootG4.crt ) to a separate internet-connected computer.
2.Transport the certificate , using your approved means, to the Luna Client host into a <downloaded cert path> location of your choice
3.Add the certificate to the certificate store using the command:
certutil -addstore -f root <downloaded cert path>
One-Step NTLS Fails on SUSE 11 Linux
Incompatibility of new Luna HSM Client components with older ones on SUSE 11 cause the one-step NTLS procedure to fail. Instead, use the multi-step procedure to establish an NTLS connection manually.
Refer to Multi-Step NTLS Connection Procedure.
Luna HSM Client No Longer Supports Luna PCIe HSM 6 on any platform
Luna HSM Client 10.5.0 and newer cannot be used with a Luna PCIe HSM 6 that might be present in the host. If you need to use a version 6.x HSM card with your application, install Luna HSM Client 10.3.0 or older for Windows, or Luna HSM Client 10.4.1 or older for Linux.
Luna HSM Client No Longer Supports Luna PCIe HSM 6 on Windows
Luna HSM Client 10.4.0 and newer cannot be used with an installed Luna PCIe HSM 6.
Support for Windows Server 2012 R2 is Ended
Luna HSM Client 10.3.0 is the last version that will support Windows Server 2012 R2.
Red Hat Enterprise Linux / CentOS 6 Support is Ended
Luna HSM Client 10.2.0 is the last version that will support RHEL 6 and related operating systems. If you plan to install future client updates, consider updating your clients to RHEL 7 or 8.
Support for 32-bit OS Platforms is Ended
Starting with Luna HSM Client 10.2.0, 32-bit libraries are no longer provided. If you have a 32-bit application or integration, remain with a previous client release
Older JAVA Versions Require Patch/Update
The .jar files included with Luna HSM Client 10.x have been updated with a new certificate, signed by the Oracle JCE root certificate. This certificate validation requires a minimum Oracle JDK/JRE version.
>If your application relies on Oracle Java 7 or 8, you must update to the advanced version provided by Oracle. You require (at minimum) version 7u131 or 8u121. Please refer to Oracle's website for more information: https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
>If your application relies on IBM Java 7 or 8, you must install a patch from IBM before updating to Luna HSM Client 10.x (see APAR IJ25459 for details).
CKR_MECHANISM_INVALID Messages in Mixed Luna Cloud HSM Implementations
When using a Luna Cloud HSM service with Luna HSM Client, you might encounter errors like "CKR_MECHANISM_INVALID" or "Error NCryptFinalizeKey" during some operations in Hybrid HA and FIPS mode (3DES Issue). This can occur if firmware versions differ between a Luna HSM partition and a Luna Cloud HSM service in an HA group when you invoke a mechanism that is supported on one but not the other. Similarly, if one member is in FIPS mode, while the other is not, a mechanism might be requested that is allowed for one member, but not the other. For example, the ms2luna tool can fail when 3DES operations are invoked.
Resolved Issue LUNA-7585: Java DERIVE and EXTRACT flag settings for keys injected into the HSM
Formerly, the DERIVE and EXTRACT flags were forced to "true" in the JNI, which overrode any values passed by applications via Java. This was resolved in Luna HSM Client 7.3.0.
As of Luna HSM Client 7.3.0:
>The default values for the DERIVE and EXTRACT flags are set to "false" (were set to “true” in previous releases).
>JNI accepts and preserves values set by applications via the following Java calls:
LunaSlotManager.getInstance().setSecretKeysDerivable( true );
LunaSlotManager.getInstance().setPrivateKeysDerivable( true );
LunaSlotManager.getInstance().setSecretKeysExtractable( true );
LunaSlotManager.getInstance().setPrivateKeysExtractable( true );
NOTE If you have existing code that relies on the DERIVE and EXTRACT flags being automatically defined by the JNI for new keys, you will need to modify your application code to set the flag values correctly.
In cases where a derived key must be extractable, add the following line to the java.security file: