Accton Technology ES4512C, ES4524C, ES4548C Configuring the Secure Shell

Configuring the Switch

Caution: For maximum security, we recommend you obtain a unique Secure Sockets

Layer certificate at the earliest opportunity. This is because the default

certificate for the switch is not unique to the hardware you have purchased.

When you have obtained these, place them on your TFTP server, and use the

following command at the switch's command-line interface to replace the default

(unrecognized) certificate with an authorized one:

Note: The switch must be reset for the new certificate to be activated. To reset the

switch, type: Console#reload

Configuring the Secure Shell

The Berkley-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

The Secure Shell (SSH) includes server/client applications intended as a secure

replacement for the older Berkley 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.

Note that you need to install an SSH client on the management station to access the

switch for management via the SSH protocol.

Note: The switch supports both SSH Version 1.5 and 2.0.

Command Usage

The SSH server on this switch supports both password and public key

authentication. If password authentication is specified by the SSH client, then the

password can be authenticated either locally or via a RADIUS or TACACS+ remote

authentication server, as specified on the Authentication Settings page

(page3-31). If public key authentication is specified by the client, then you must

configure authentication keys on both the client and the switch as described in the

following section. Note that regardless of whether you use public key or password

authentication, you still have to generate authentication keys on the switch (SSH

Host Key Settings) and enable the SSH server (Authentication Settings).

Console#copy tftp https-certificate 4-63

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>