Compatibility issues

Some compatibility issues must be noted when using KMU with

• ProtectToolkit-J

• ProtectToolkit-C V4.0, V3.x, and V2.x

Using KMU with ProtectToolkit-J

ProtectToolkit-J is SafeNet’s Java Cryptography Architecture (JCA) and Java Cryptography Extension provider (JCE) software.

KMU can be used to set up tokens and keys for use with ProtectToolkit-J V3 or later. The tokens and keys that are managed with KMU are fully compatible and can be utilized by ProtectToolkit-J. The KMU can also be used to see and manipulate keys that have been created by ProtectToolkit-J. For more information, see Key management.

Please contact Thales for further details on its SafeNet ProtectToolkit-J products.

Using KMU with ProtectToolkit-C V4.0, V3.x, and V2.x

This version of the KMU is not compatible for use with ProtectToolkit-C version 4.0 or less.

The KMU can read backup files and smart cards created by ProtectToolkit-C v2.x and v3.x but cannot create backup cards/files for these older versions.

The ctkmu command line utility is capable of creating backup cards/files for ProtectToolkit-C v4.0 and V3.x HSMs. So, if you are exporting keys from a system running ProtectToolkit-C 4.1 or above for import to an older system then use the ctkmu and the -3 option.

Please contact Thales for a KMU that is compatible with older versions of this software.