SSH - Secure Shell Security Management
SSH - Secure Shell
Authentication, also referred to as user identity, is the means by which a system verifies that
access is only given to intended users and denied to anyone else. All machines that
implement the SSH protocol (e.g. Management Host with MetaASSIST View or the ML
device) support authentication and therefore must own a pair of encryption keys - one public
and one private. Encryption capability is always provided on the data path. Authentication
however, can be enabled or disabled (by default) in the ML device running as an SSH Server.
SSH protocol provides authentication, encryption and data integrity to secure network
communication between management host and the ML device as follows:
Authentication - ML device supports DSA authentication keys 512, 768, or 1024 bits
long.
Encryption - ML device employs symmetric keys encryption algorithms: AES, DES,
3DES, Blowfish. Encryption is always enabled, whether authentication is enabled or
disabled.
Data integrity - ML device automatically (not-configurable) provides the Message
Authentication Code (MAC) algorithm.
NOTE: SSH is not applied to Craft port connection.
When authentication is disabled in the ML230/ML2300 system, then authentication from any
management host (running as an SSH client) is allowed.