C
HAPTER
14
| Security Measures
Configuring the Secure Shell
– 289 –
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 161: Downloading the Secure-Site Certificate
CONFIGURING THE SECURE SHELL
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.
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.
N
OTE
:
You need to install an SSH client on the management station to
access the switch for management via the SSH protocol.
N
OTE
:
The switch supports both SSH Version 1.5 and 2.0 clients.
To Next Page
Loading...
Need help?
General