360
Publickey authentication
The server authenticates a client by verifying the digital signature of the client. The publickey
authentication process is as follows:
1.
The client sends the server a publickey authentication request that includes the username,
public key, and public key algorithm name.
If the digital certificate of the client is required in authentication, the client also encapsulates the
digital certificate in the authentication request. The digital certificate carries the public key
information of the client.
2.
The server verifies the client's public key.
{
If the public key is invalid, the server informs the client of the authentication failure.
{
If the public key is valid, the server requests the digital signature of the client. After receiving
the signature, the server uses the public key to verify the signature and informs the client of
the authentication result.
When acting as an SSH server, the device supports using the public key algorithms DSA, ECDSA,
and RSA to verify digital signatures.
When acting as an SSH client, the device supports using the public key algorithms DSA, ECDSA,
and RSA to generate digital signatures.
For more information about public key configuration, see "
."
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.
Any authentication
The server requires clients to pass password authentication or publickey authentication.
SSH support for Suite B
Suite B contains a set of encryption and authentication algorithms that meet high security
requirements.
lists all algorithms in Suite B.
The SSH server and client support using the X.509v3 certificate for identity authentication in
compliance with the algorithm, negotiation, and authentication specifications defined in RFC 6239.
Table 23 Suite B algorithms
Security
level
Key exchange
algorithm
Encryption algorithm
and HMAC algorithm
Public key algorithm
128-bit ecdh-sha2-nistp256 aes128-gcm
x509v3-ecdsa-sha2-nistp256
x509v3-ecdsa-sha2-nistp384
192-bit ecdh-sha2-nistp384 aes256-gcm x509v3-ecdsa-sha2-nistp384
Both
ecdh-sha2-nistp256
ecdh-sha2-nistp384
aes128-gcm
aes256-gcm
x509v3-ecdsa-sha2-nistp256
x509v3-ecdsa-sha2-nistp384
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 and non-FIPS mode. For more
information about FIPS mode, see "
."
Содержание FlexFabric 5940 SERIES
Страница 251: ...238 ...