Ericsson ECN330, User Manual

Page: 142 / 1226

Configuring the ECN330-switch
136
1553-KDU 137 365 Uen D 2006-06-16
Command Usage
The SSH server on the ECN330-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 through a RADIUS or
remote authentication server, as specified on the Authentication
Settings page (page 128). If public key authentication is specified by the client,
then authentication keys must be configured on both the client and the ECN330-
switch as described in the following section. Note that regardless of whether
public key or password authentication is used, authentication keys still have to
be generated on the ECN330-switch (SSH Host Key Settings) and enable the
SSH server (Authentication Settings).
To use the SSH server, complete these steps:
1. Generate a Host Key Pair – On the SSH Host Key Settings page, create a
host public/private key pair.
2. Provide Host Public Key to Clients – Many SSH client programs
automatically import the host public key during the initial connection setup
with the ECN330-switch. Otherwise, a known hosts file needs to be
manually created on the management station and the host public key placed
in it. An entry for a public key in the known hosts file would appear similar to
the following example:
10.1.0.54 1024 35 1568499540186766925933394677505461732531367
4890836547254 1502024559319986854435836165199992332978176606
5830956 10825913212890233 765468017262725714134287629413011
96195566782 59566410486957427888146206 51941746772984865468
61571773939016477935594230357741309802273708779454524083971
752646358058176716709574804776117
3. Import Client’s Public Key to the ECN330-switch – Use the
copy tftp
public-key
command (page 651) to copy a file containing the public key
for all the SSH client’s granted management access to the ECN330-switch.
(Note that these clients must be configured locally on the ECN330-switch
through the User Accounts page as described on page 126.) The clients are
subsequently authenticated using these keys. The current firmware only
accepts public key files based on standard UNIX format as shown in the
following example for an RSA Version 1 key:
1024 35 134108168560989392104094492015542534763164192187295
8921143173880 055536161631051775940838686311092912322268285
19254374603100937187721199696317813662774141689851320491172