Do not set 0.0.0.0 as a network route destination. Problem: It is possible to add 0.0.0.0 as a network route on the appliance. You must add map_aes_cmac_general_old=1 to the Toggles section of the nf/ cryptoki.ini file. Resolved: Fixed in Luna HSM Client 10.7.0. Workaround: Use Luna HSM Client 10.4.1 instead.

Problem: When using Luna HSM Client 10.5.x or 10.6.0 to migrate a master key from a local keystore to a Luna HSM, the key is successfully migrated but operations fail with the log error Unknown Mechanism Type. Workaround: Turn ActiveEnhanced mode back on manually using LunaCM ( hagroup recoverymode -mode activeEnhanced). Problem: After deleting an HA group, ActiveEnhanced mode is turned off and the client returns to ActiveBasic mode. Key migration to Luna HSM Firmware 7.8.4 is only possible in non-FIPS mode. Problem: Using Luna HSM Firmware 7.8.4 in FIPS mode, migration of keys from a Microsoft provider to Luna provider using the ms2luna utility fails with error CKR_MECHANISM_INVALID. Issues listed in green have been resolved and the component and version including the fix is provided. Use the buttons below to display issues related to specific Luna software/firmware components. Workarounds are provided where available.

The following table lists known issues in all released versions of Luna 7 components. These archived documents are not updated, and may contain errors and omissions. Select a release to view the available documentation for the release. Older versions of the documentation are release-specific. You are viewing the latest version of the Luna Network HSM 7 documentation, which covers all released Luna Network HSM 7 and Luna HSM Client 7/10 components, and is updated frequently with the latest corrections and improvements.

Free for mac download CopyQ 7.1.0