Configuring The Secure Shell; Figure 3-48 Https Settings - TP-Link TL-SL5428 User Manual

• Source Certificate File Name – Specifies the name of certificate file as stored on
the TFTP server.
• Source Private File Name – Specifies the name of the private key file as stored
on the TFTP server.
• Private Password – The password for the private key file.
Web – Click Security, HTTPS Settings. Fill in the TFTP server, certificate and private
file name details, then click Copy Certificate.
CLI – This example copies the certificate file from the designated TFTP server.
Console#copy tftp https-certificate
TFTP server ip address: <server ip-address>
Source certificate file name: <certificate file name>
Source private file name: <private key file name>
Private password: <password for private key>
Note:
The switch must be reset for the new certificate to be activated. To reset the
switch, See "Resetting the System" on page 3-33 or type:

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
AAA Authorization and Accounting

Figure 3-48 HTTPS Settings

4-84
Console#reload
3-71
3