Supermicro SSE-G2252 User Manual page 313

The Secure Shell (SSH) includes server/client applications intended as a secure
replacement for the older Berkeley remote access tools. SSH can also provide remote
management access to this switch as a secure replacement for Telnet. When the client
contacts the switch via the SSH protocol, the switch generates a public-key that the
client uses along with a local user name and password for access authentication. SSH
also encrypts all data transfers passing between the switch and SSH-enabled
management station clients, and ensures that data traveling over the network arrives
unaltered.
NOTE: You need to install an SSH client on the management station to access
the switch for management via the SSH protocol.
NOTE: The switch supports both SSH Version 1.5 and 2.0 clients.
Command Usage
The SSH server on this switch supports both password and public key authentication. If
password authentication is specified by the SSH client, then the password can be
authenticated either locally or via a RADIUS or TACACS+ remote authentication server,
as specified in "Configuring Local/Remote Logon Authentication" on page
key authentication is specified by the client, then you must configure authentication keys
on both the client and the switch as described in the following section. Note that
regardless of whether you use public key or password authentication, you still have to
generate authentication keys on the switch (SSH Host Key Settings) and enable the
SSH server (Authentication Settings).
To use the SSH server, complete these steps:
1. Generate a Host Key Pair – On the SSH Host Key Settings page, create a host
public/private key pair.
2. Provide Host Public Key to Clients – Many SSH client programs automatically
import the host public key during the initial connection setup with the switch.
Otherwise, you need to manually create a known hosts file on the management
station and place the host public key in it. An entry for a public key in the known
hosts file would appear similar to the following example:
10.1.0.54 1024 35
15684995401867669259333946775054617325313674890836547254
15020245593199868544358361651999923329781766065830956
10825913212890233 76546801726272571413428762941301196195566782
5956641048695742788814620651941746772984865468615717739390164779355942
30357741309802273708779454524083971752646358058176716709574804776117
3. Import Client's Public Key to the Switch – See
page 14-40, or use the
containing the public key for all the SSH client's granted management access to the
switch. (Note that these clients must be configured locally on the switch via the User
copy tftp public-key command
14-35
Chapter 14: Security Measures
"Importing User Public Keys" on
(page 21-15) to copy a file
14-3. If public