Fixed an issue where subscription details were not returned in the DPoD management portal for Service Provider users.
Fixed an issue where subscription details were not returned in the DPoD management portal for Service Provider users.
The Luna Cloud HSM client bundle is updated to include the 10.9.0 Universal Client. Users are encouraged to upgrade to this latest client version and ensure it is supported in accordance with the Universal Client Supported Versions with Luna Cloud HSM table.
See Upgrade Client for more information about upgrading your client.
Bugs fixed
Resolved an Invalid memory access issue when running on a Windows Cloud Plugin.
Fixed Issue: Resolved a problem that prevented some users from viewing Luna Cloud HSM snapshots. This fix enhances the user experience and ensures that all snapshots are accessible as intended.
FW 2.0.5 has been released to all production environments. This release resolves the issue with restoring Luna Cloud HSM backups from a Luna USB Backup HSM.
The new firmware versions based on region and FIPS mode are as follows:
Added
The issue with restoring Luna Cloud HSM backups from a Luna USB Backup HSM has been rectified with FW 2.0.5.
An issue was found with the Luna Cloud HSM Support Tool version 1.0.0 where incorrect data was reported for datacentre connectivity in some cases.
This issue has been fixed with the Luna Cloud HSM Support Tool version 1.0.2.
Luna Cloud HSM Support Tool version 1.0.2 addresses the following bug:
FW 2.0.2 has been released to all production environments. This release resolves an issue that prevented cloning objects between two Luna Cloud HSM partitions when using the 10.5 client.
The new firmware versions based on region and FIPS mode are as follows:
FW 2.0.2 includes the following bug fixes:
Cloning keys between two Luna Cloud HSM partitions fails when using the 10.5 client. There are currently two possible workaround scenarios.
-> Workaround #1 - If there is a Luna SA7 (or any other separate device to use as an intermediary for the cloning) then clone to and from that device.
-> Workaround #2 - If there is no separate device then completely uninstall the 10.5 client and install the 10.4 client from scratch. For this option please raise a support ticket to the Thales Customer Support portal to request to join the 2 partitions together as the 10.4 client does not support dynamic partition loading.
In UC 10.4, a bug was found when using CKLog in Linux with a Luna Cloud HSM client package. The output was spammed with "LunaNamedSystemMutex: open() failed: No such file or directory".
In the UC 10.5 client, the new mutex folder will use the /lock directory which solves this issue.
The firmware versions for Luna Cloud HSM Services operating in NA environments have been updated. The current firmware version based on region and FIPS mode are as follows:
FW 1.5 includes improvements to the Point to Point encryption service. FW 1.5 also includes the following bug fixes:
Added
Bugs Found
cmu verifyhsm does not prompt the user to enter a challenge string. Always specify a challenge string using cmu verifyhsm -challenge <string>.cmu requestcertificate using the wrong attribute to specify the private key returns an incorrect error message. Use the -privateouid to specify a private key on a Luna Cloud HSM service.cmu import to import a DSA key fails. Use an RSA public key instead.cmu selfsigncertificate with no arguments specified, on Linux, cmu fails to prompt the user for the relevant object handles/OUIDs. Always specify the object handles/OUIDs using -publichandle and -privatehandle or -publicouid and -privateouid.ckmdeo option Get OUID (39) returns OUIDs with extra zeroes appended. Use option Get Attribute (24) to view the correct OUID.CKR_OBJECT_HANDLE_INVALID. We recommend you avoid upgrading your Luna Cloud HSM service client until the issue is resolved. cmu getpkc to confirm a public key can fail. Execute the ckdemo Display Object (27) function to confirm the key pairs origins and security in the HSM. If the CKA_NEVER_EXTRACTABLE attribute is present it confirms that the private key was created in the HSM and has never been extracted.Bugs Fixed
cmu selfsigncertificate now match the input serial number.Added
Bugs Found
Bugs Fixed