NetApp
Configuration : Security > SSH/SSL : Understanding SSH and SSL : The SSH protocol

The SSH protocol
SSH improves security by providing a means for a storage system to authenticate the client and by generating a session key that encrypts data sent between the client and storage system. SSH performs public-key encryption using a host key and a server key.
Data ONTAP supports password authentication and public-key-based authentication. Data ONTAP does not support the use of a .rhosts file or the use of a .rhosts file with RSA host authentication.
Data ONTAP supports the following encryption algorithms:
•
•
•
•
Data ONTAP supports the SSH 1.x protocol and the SSH 2.0 protocol.
Data ONTAP supports the following SSH clients:
•
•
•
•
•
SSH uses three keys to improve security:
•
SSH uses the host key to encrypt and decrypt the session key. You determine the size of the host key, and Data ONTAP generates the host key when you configure SecureAdmin.
Note: SecureAdmin is set up automatically on storage systems shipped with Data ONTAP 8.0 or later.
•
SSH uses the server key to encrypt and decrypt the session key. You determine the size of the server key when you configure SecureAdmin. If SSH is enabled, Data ONTAP generates the server key when any of the following events occur:
•
•
•
•
SSH uses the session key to encrypt data sent between the client and storage system. The session key is created by the client. To use the session key, the client encrypts the session key using the host and server keys and sends the encrypted session key to the storage system, where it is decrypted using the host and server keys. After the session key is decrypted, the client and storage system can exchange encrypted data.
The following table shows how Data ONTAP creates a secure session between the storage system and client.
If you are logged into a non-root user account on a client, and you request a list of supported SSH commands on a storage system using the ssh <ip address> ? command, some SSH clients do not pass the ? (question mark) to the storage system. To make sure the client passes the question mark, wrap the ? in quotes, for example, ssh <ip address> ’?’.
Note: Some characters, for example ?, ., *, and ^, can have special meaning for the command interpreter running on the client. The client command interpreter might replace the character with an environment-specific value prior to passing it to the SSH program. To prevent a replacement, use an escape sequence before the character (for example, ssh <ip address> \?) or enclose the character in quotes.


Was this topic helpful? Send comments to NetApp.