Version Dependencies by Feature

Some of the SafeNet Luna Network HSM functionality described in the documentation has been introduced in updates since the initial product release. For your own reasons, you may wish to apply some aspects of a product update and not others. For example:

>you may choose to update appliance or client software while keeping an earlier firmware version

>if you are maintaining a large number of client workstations, it may be cumbersome to apply software updates to all of them

The following table outlines the SafeNet Luna Network HSM functions that depend on a certain software/firmware version, or have other requirements you must consider.

Function	Version Requirements	Notes
Improved Luna HSM Client: >Version-Compatible Luna HSM Client (Luna HSMs version 6.3 and higher) >Modify Luna HSM Client installed components in the Windows installer (Modifying the Installed Luna HSM Client Software) >User-Defined Luna HSM Client install paths >Luna Minimal Client (for Linux)	Client: 7.2	Minimal Client does not include tools, and is intended for customer application containers connecting to the Network HSM. A separate full Luna HSM Client installation and configuration must be performed on the container host (and the resulting config file and certificate folders saved on the host), to establish NTLS or STC connections for use by the containers.
Initialize the orange RPV key remotely (Remote RPV Initialization)	Firmware: 7.2.0 Appliance: 7.2 Client: 7.2
Configure Cipher Suites (sysconf tls ciphers)	Appliance: 7.2 Client: 7.2	The Luna 7.2 appliance update includes the sysconf tls ciphers LunaSH commands, but you must update Luna HSM Client to use any of the newly-included ciphers. For older clients, the ciphers available for negotiation are those that are common to your client version and to the updated Network HSM.
Customize system logging by severity level (Customizing Severity Levels or Customizing Remote Logging Severity Levels)	Appliance: 7.2	If you were using remote logging before you upgraded the appliance software to 7.2, you must delete any existing remote hosts (see syslog remotehost delete) and re-add them before you can customize severity levels.
Rename/Relabel partitions (partition rename and partition changelabel)	Firmware: 7.2.0 Appliance: 7.2 Client: 7.2
Crypto User can clone public objects	Firmware: 7.2.0	The Crypto User (CU) role has always been able to create public objects, but not clone them. In HA mode, this would cause the replication and subsequent object creation operations to fail. Firmware 7.2.0 allows the CU to clone public objects, and therefore to perform operations on HA groups without Crypto Officer authentication.
Configure partition policies for export of private keys (Keys In Hardware vs. Private Key Export)	Firmware: 7.1.0	You can configure partition policies for Cloning or Key Export Mode manually, as long as you have updated the HSM firmware. To set these modes using Policy Templates, you must meet the Policy Template requirements.
Policy Templates (Policy Templates)	Firmware: 7.1.0 Appliance: 7.1 Client: 7.1