
162
•
Password-publickey authentication
—The server requires SSH2 clients to pass both password
authentication and publickey authentication. However, an SSH1 client only needs to pass either
authentication, regardless of the requirement of the server.
•
Any authentication
—The server requires clients to pass either password authentication or publickey
authentication.
FIPS compliance
The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features,
commands, and parameters might differ in FIPS mode (see "
") and non-FIPS mode.
Configuring the device as an SSH server
You can configure the device as an Stelnet, SFTP, or SCP server. Because the configuration procedures
are similar, the SSH server represents the Stelnet, SFTP, or SCP server unless otherwise specified.
SSH
server configuration task list
Tasks at a glance
Remarks
Generating local DSA or RSA key pairs
N/A
Enabling the SSH server function
Required for Stelnet and SCP servers.
Enabling the SFTP server function
Required for SFTP server.
Configuring the user interfaces for Stelnet
N/A
Configuring a client's host public key
Required if the authentication method is
publickey
,
password-publickey,
or
any
.
Configuring the PKI domain for verifying the client
certificate
See "
."
Required if publickey authentication is configured
for users and if the clients send the public keys to
the server through digital certificates for validity
check.
The PKI domain must have the CA certificate to
verify the client certificate.
(Required/optional.)
Required if the authentication method is
publickey
,
password-publickey,
or
any
.
Optional if the authentication method is
password
.
Setting the SSH management parameters
Generating local DSA or RSA key pairs
IMPORTANT:
Do not generate the local DSA key pair when the device operates in FIPS mode as an SSH server. User
authentication will fail because the SSH server operating in FIPS mode supports only RSA key pairs.