Brocade Fabric OS Administrator's Guide - Supporting Fabric OS v7.0.1 (53-1002446-01, March 2012)
Fabric OS Administrator’s Guide 117
53-1002446-01
Secure Shell protocol
6
3. Type y or yes at the cfgload attributes prompt.
4. Type y or yes at the Enforce secure configUpload/Download prompt.
Example of setting up SCP for configUpload/download
switch:admin> configure
Not all options will be available on an enabled switch.
To disable the switch, use the "switchDisable" command.
Configure...
System services (yes, y, no, n): [no] n
ssl attributes (yes, y, no, n): [no] n
http attributes (yes, y, no, n): [no] n
snmp attributes (yes, y, no, n): [no] n
rpcd attributes (yes, y, no, n): [no] n
cfgload attributes (yes, y, no, n): [no] y
Enforce secure config Upload/Download (yes, y, no, n): [no] y
Enforce signature validation for firmware (yes, y, no, n): [no]
Secure Shell protocol
To ensure security, Fabric OS supports secure shell (SSH) encrypted sessions. SSH encrypts all
messages, including the client transmission of the password during login. The SSH package
contains a daemon (sshd), which runs on the switch. The daemon supports a wide variety of
encryption algorithms, such as Blowfish-Cipher block chaining (CBC) and Advanced Encryption
Standard (AES).
NOTE
To maintain a secure network, you should avoid using Telnet or any other unprotected application
when you are working on the switch.
Commands that require a secure login channel must originate from an SSH session. If you start an
SSH session, and then use the login command to start a nested SSH session, commands that
require a secure channel will be rejected.
Fabric OS supports OpenSSH protocol v2.0 (ssh2). For more information on SSH, refer to the SSH
IETF website:
http://www.ietf.org/ids.by.wg/secsh.html
You can also refer to SSH, The Secure Shell: The Definitive Guide by Daniel J. Barrett, Ph. D.,
Richard E. Silverman, and Robert G. Byrnes.
SSH public key authentication
OpenSSH public key authentication provides password-less logins, known as SSH authentication,
that uses public and private key pairs for incoming and outgoing authentication. This feature allows
only one allowed-user to be configured to utilize outgoing OpenSSH public key authentication.Any
admin user can perform incoming Open SSH public key authentication. Using OpenSSH RSA and