237
Configuration task list
Public key configuration tasks enable you to manage the local asymmetric key pairs, and configure the
peer host public keys on the local device. By completing these tasks, the local device is ready to work
with applications such as SSH and SSL to implement data encryption/decryption, or digital signature.
Complete these tasks to configure public keys:
Task Remarks
Configuring a local
asymmetric key pair
on the local device.
Creating a local asymmetric key pair
Perform the tasks as
needed.
Displaying or exporting the local host public key
Destroying a local asymmetric key pair
Specifying the peer public key on the local device
Creating a local asymmetric key pair
When you create an asymmetric key pair on the local device, follow these guidelines:
•
Create an asymmetric key pair of the proper type to work with a target application.
•
After you enter the command, specify a proper modulus length for the key pair. The following table
compares the three types of key pairs.
Type
Number of key pairs
Modulus length
Remarks
RSA (in
non-FIPS
mode)
Two key pairs, one server key pair and one
host key par. Each key pair comprises a
public key and a private key.
512 to 2048 bits.
1024 by default.
To achieve high
security, specify at least
768 bits.
RSA
(in FIPS
mode)
One key pair, the host key pair.
2048 bits.
N/A
DSA (in
non-FIPS
mode)
One key pair, the host key pair.
512 to 2048 bits.
1024 by default.
To achieve high
security, specify at least
768 bits.
DSA
(in FIPS
mode)
One key pair, the host key pair.
1024 to 2048 bits.
1024 by default.
N/A
To create a local asymmetric key pair:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a local asymmetric key
pair.
public-key local create
{
dsa
|
rsa
}
By default, no asymmetric key pair
is created.
Key pairs created with the
public-key local create
command
are saved automatically and can
survive system reboots.
