Configuring Secure Shell (SSH)
Configuring the Switch for SSH Operation
1. Assigning a Local Login (Operator) and
Enable (Manager) Password
At a minimum, ProCurve recommends that you always assign at least a
Manager password to the switch. Otherwise, under some circumstances,
anyone with Telnet, web, or serial port access could modify the switch’s
configuration.
To Configure Local Passwords. You can configure both the Operator and
Manager password with one command.
Syntax: password < manager | operator | all >
Figure 7-4. Example of Configuring Local Passwords
2. Generating the Switch’s Public and Private Key Pair
You must generate a public and private host key pair on the switch. The switch
uses this key pair, along with a dynamically generated session key pair to
negotiate an encryption method and session with an SSH client trying to
connect to the switch.
The host key pair is stored in the switch’s flash memory, and only the public
key in this pair is readable. The public key should be added to a "known hosts"
file (for example, $HOME/.ssh/known_hosts on UNIX systems) on the
SSH clients which should have access to the switch. Some SSH client appli-
cations automatically add the switch’s public key to a "known hosts" file. Other
SSH applications require you to manually create a known hosts file and place
the switch’s public key in the file. (Refer to the documentation for your SSH
client application.)
(The session key pair mentioned above is not visible on the switch. It is a
temporary, internally generated pair used for a particular switch/client ses-
sion, and then discarded.)
7-10
To Next Page
Loading...
Need help?
General