Clone key, Import key, 132 import key – HP Secure Key Manager User Manual
Page 132: Viewing the clone key section, Clone key section components, Import keys
Description
Component
When selected, the key contains multiple versions, up to a maximum of 4000. Each
key version has unique key bytes, but shared key metadata (key name, algorithm,
permissions, etc. The first key version is created when the key is created. Additional
key versions may be created later using the Key Versions section.
Versioned Key Bytes
Select an existing key to copy its group permissions. The new key and the existing key
must be of compatible types; specifically, they must both use RSA, both use HmacSHA1,
or they may use either AES, DES, or RC4.
Copy Group Permis-
sions From
Click Create to create the key.
Create
Clone Key
Use this section to assign the key bytes and key metadata from an existing key to a new key. You
can choose to copy or ignore the existing group permissions and custom attributes. You can also use
this section to create a versioned key from a non-versioned key.
Figure 57 Viewing the Clone Key section
Table 38 Clone Key section components
Description
Component
This is the name that the server uses to refer to the new key. The key name must begin
with a letter, it must be between 1 and 64 characters (inclusive), and it can consist of
letters, numbers, underscores (_), periods (.), and hyphens (-).
New Key Name
This is the key that will be copied.
Key Cloned From
Select Copy from original key to use the same key bytes or select Create versioned key
bytes from non-versioned key to create a new versioned key based on the metadata
from the cloned key: the new key will not share key bytes with the copied key.
Key Bytes
Select this option to copy the group permissions from the existing key.
Copy Group Permis-
sions
Select this option to copy the custom attributes from the existing key.
Copy Custom Attrib-
utes
Click Clone to create a copy of the key.
Clone
Import Key
The Import Key section allows you to import clear text keys on SKMs. Asymmetric keys must be imported
in PEM-encoded ASN.1 DER-encoded PKCS #1 format, and both the public and private keys must
be imported. Symmetric keys must be in Base 16 format, and in the case of DES keys, parity bits must
be properly set.
Using the Management Console
132