Configuring the client public key on the server, Configuring the client public key on the server -9 – H3C Technologies H3C WX3000 Series Unified Switches User Manual
Page 481
46-9
z
You can configure a login header only when the service type is stelnet. For configuration of service
types, see
Specifying a Service Type for an SSH User
z
For details of the header command, see the corresponding section in Login in H3C WX3000 Series
Unified Switches Switching Engine Command Reference
.
Configuring the Client Public Key on the Server
This configuration is not necessary if the password authentication mode is configured for SSH users.
With the publickey authentication mode configured for an SSH client, you must configure the client’s
RSA or DSA host public key(s) on the server for authentication.
You can manually configure the public key or import it from a public key file. In the former case, you can
manually copy the client’s public key to the server. In the latter case, the system automatically converts
the format of the public key generated by the client to complete the configuration on the server, but the
client’s public key should be transferred from the client to the server beforehand through FTP/TFTP.
Follow these steps to configure the client’s public key manually:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter public key view
public-key peer keyname
Required
Enter public key edit view
public-key-code begin
—
Configure a public key for the client Enter the content of the public key
When you input the key data,
spaces are allowed between the
characters you input (because the
system can remove the spaces
automatically); you can also press
the next line. But the key you input
should be a hexadecimal digit
string coded in the public key
format.
Return to public key view from
public key edit view
public-key-code end
—
Exit public key view and return to
system view
peer-public-key
end
—