Known Issue: Luna Cloud HSM Object Accessibility After Snapshot Restoration with Fragment Key Rotation

  • Issue Overview: Objects created after a fragment key rotation event (such as destructive policy change, PIN change, partition zeroization, or re-initialization) may become inaccessible if a snapshot is restored.

Further information: For full technical details and recommended mitigation steps, please refer to KB0030646 on the Thales support portal (login required).

Luna Cloud HSM Releases 10.9.0 Luna Client

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. 


Snapshot Access Fix

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.

Luna Cloud HSM Releases FW 2.0.5 Upgrade

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: 

  • NA FIPS - 2.0.5
  • NA non-FIPS - 2.0.5
  • EU FIPS - 2.0.5
  • EU non-FIPS - 2.0.5

Added 

Luna Cloud HSM Backup

The issue with restoring Luna Cloud HSM backups from a Luna USB Backup HSM has been rectified with FW 2.0.5.

Removed Service Provider Tenant Usage Report and Associated Endpoints

The Service Provider Tenant Usage Report and the associated tenants/usageReport, tenants/usageDetails, and service_instances/usageDetails endpoints have been removed from the platform.

As an alternative use the Service Report in the DPoD service provider tenant or the /v1/service_instances/usageBillingReport endpoint, and the  /v1/backoffice/serviceAgreements{tenantId} endpoint to compile tenant usage information.

The Support Tool Has Been Upgraded

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: 

  • LCH-1498 - Support Tool reports incorrect info due to AuthN Changes.

Luna Cloud HSM Releases FW 2.0.2 Upgrade

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: 

  • NA FIPS - 2.0.2
  • NA non-FIPS - 2.0.2
  • EU FIPS - 2.0.2
  • EU non-FIPS - 2.0.2

FW 2.0.2 includes the following bug fixes:

  • LCH-489 - CPv4 Cloning command permissions incorrect for pre-FW-2.0 partitions.
  • DPS-10104 - Luna Cloud HSM Partition Cloning Fails with the 10.5 Client

    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.


Luna Cloud HSM Partition Cloning Fails with the 10.5 Client

Bugs Found 

  • DPS-10104 - Luna Cloud HSM Partition Cloning Fails with the 10.5 Client
    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.
    You can make the request by following this link:
    https://thalesdocs.com/dpod/resources/client_resources/client_connect_to_multiple_services/index.html

Mutex Error Message When Using CKLog Fixed in UC 10.5

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.

Show Previous EntriesShow Previous Entries