Table of Contents
Advertisement
Chapter 12
| Security Measures
Configuring the Secure Shell
Configuring the Secure Shell
◆
Private Password – Password stored in the private key file. This password is
used to verify authorization for certificate use, and is verified when
downloading the certificate to the switch.
◆
Confirm Password – Re-type the string entered in the previous field to ensure
no errors were made. The switch will not download the certificate if these two
fields do not match.
Web Interface
To replace the default secure-site certificate:
1.
Click Security, HTTPS.
2.
Select Copy Certificate from the Step list.
3.
Fill in the TFTP server, certificate and private key file name, and private
password.
4.
Click Apply.
Figure 180: Downloading the Secure-Site Certificate
The Berkeley-standard includes remote access tools originally designed for Unix
systems. Some of these tools have also been implemented for Microsoft Windows
and other environments. These tools, including commands such as rlogin (remote
login), rsh (remote shell), and rcp (remote copy), are not secure from hostile attacks.
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.
– 282 –
Advertisement
Table of Contents
