116
Creating a local key pair
Configuration guidelines
When you create a local key pair, follow these guidelines:
•
The key algorithm must be the same as required by the security application.
•
The key modulus length must be appropriate (see
). The longer the key modulus length, the
higher the security, and the longer the key generation time.
•
If you do not assign the key pair a name, the system assigns the default name to the key pair and
marks the key pair as
default
. You can also assign the default name to another key pair, but the
system does not mark the key pair as
default
.
•
The name of a key pair must be unique among all manually named key pairs that use the same key
algorithm, but can be the same as a key pair that uses a different key algorithm. If a name conflict
occurs, the system asks whether you want to overwrite the existing key pair.
•
The key pairs are automatically saved and can survive system reboots.
Table 8
A comparison of different types of asymmetric key algorithms
Type
Number of key pairs
Modulus length
H3C
recommendation
RSA (in non-FIPS
mode)
•
If you specify a key pair name, the
command creates a host key pair.
•
If you do not specify a key pair name,
the command creates one server key
pair and one host key pair, and both
key pairs use their default names.
512 to 2048 bits.
1024 by default.
At least 768 bits.
RSA
(in FIPS mode)
If you do not specify a key pair name, the
command only creates a host key pair,
and the key pair uses the default name.
2048 bits.
N/A
DSA (in non-FIPS
mode)
The command only creates one host key
pair.
512 to 2048 bits.
1024 by default.
At least 768 bits.
DSA
(in FIPS mode)
The command only creates one host key
pair.
2048 bits.
N/A
ECDSA
The command only creates one host key
pair.
192 bits.
N/A
NOTE:
Only SSH 1.5 uses the RSA server key pair.
Configuration procedure
To create a local key pair:
Step Command
Remarks
1.
Enter system view.
system-view
N/A