Configuring Secure Shell (SSH)

Further Information on SSH Client Public-Key Authentication

Copying a client-public-key into the switch requires the following:

■One or more client-generated public keys. Refer to the documentation provided with your SSH client application.

■A copy of each client public key (up to ten) stored in a single text file or individual on a TFTP server to which the switch has access. Terminate all client public-keys in the file except the last one with a <CR><LF>.

Note on Public The actual content of a public key entry in a public key file is determined by

Keysthe SSH client application generating the key. (Although you can manually add or edit any comments the client application adds to the end of the key, such as the smith@fellow at the end of the key in figure 6-14on page 6-24.)

Syntax: copy tftp pub-key-file <ip-address> <filename> [<append manager operator>]

Copies a public key file from a TFTP server into flash memory in the switch.

The append option adds the key(s) for operator access.

The manager option replaces the key(s) for manager access; follow with the append option to add the key(s).

The operator option replaces the key(s) for operator access (default); follow with the append option to add the key(s).

show crypto client-public-key [manager operator] [keylist-str] [babble fingerprint]

Displays the client public key(s) in the switch’s current client-public-key file.

The manager option selects the manager public keys.

The operator option selects operator public keys.

The keylist-stroption allows you to select keys to display (a comma-delimited list).

The babble option converts the key data to phonetic hashes that are easier for visual comparisons.

The fingerprint option converts the key data to hexadecimal hashes that are for the same purpose.

6-26