U
SER
A
UTHENTICATION
C
OMMANDS
21-22
Configuration Guidelines
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
remote authentication server, as specified by the
authentication login
command on page 21-5. 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 and enable the SSH server.
To use the SSH server, complete these steps:
1.
Generate a Host Key Pair – Use the
ip ssh crypto host-key generate
command to 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 switch. Otherwise, you need to manually create a known
hosts file on the management station and place the host public key 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 15684995401867669259333946775054617325313674890836547254
15020245593199868544358361651999923329781766065830956 10825913212890233
76546801726272571413428762941301196195566782 59566410486957427888146206
519417467729848654686157177393901647793559423035774130980227370877945452408397
1752646358058176716709574804776117
3.
Import Client’s Public Key to the Switch – Use the
copy tftp
public-key
command
to copy a file containing the public key for all the
SSH client’s granted management access to the switch. (Note that these
clients must be configured locally on the switch with the
username
command as described on page 21-2.) 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 key:
Summary of Contents for 7824M/FSW - annexe 1
Page 2: ......
Page 24: ...TABLE OF CONTENTS xxiv ...
Page 28: ...TABLES xxviii ...
Page 32: ...FIGURES xxxii Figure 16 3 DNS Cache 16 7 ...
Page 34: ...GETTING STARTED ...
Page 46: ...SYSTEM DEFAULTS 1 12 ...
Page 62: ...SWITCH MANAGEMENT ...
Page 74: ...CONFIGURING THE SWITCH 3 12 ...
Page 112: ...BASIC MANAGEMENT TASKS 4 38 ...
Page 168: ...USER AUTHENTICATION 6 30 ...
Page 223: ...SHOWING PORT STATISTICS 9 33 Figure 9 12 Port Statistics ...
Page 230: ...ADDRESS TABLE SETTINGS 10 6 ...
Page 304: ...CLASS OF SERVICE 13 16 ...
Page 316: ...QUALITY OF SERVICE 14 12 ...
Page 338: ...MULTICAST FILTERING 15 22 ...
Page 346: ...DOMAIN NAME SERVICE 16 8 ...
Page 348: ...COMMAND LINE INTERFACE IP Interface Commands 35 1 ...
Page 362: ...OVERVIEW OF COMMAND LINE INTERFACE 17 14 ...
Page 494: ...USER AUTHENTICATION COMMANDS 21 48 ...
Page 514: ...CLIENT SECURITY COMMANDS 22 20 ...
Page 540: ...ACCESS CONTROL LIST COMMANDS 23 26 ...
Page 558: ...INTERFACE COMMANDS 24 18 ...
Page 576: ...MIRROR PORT COMMANDS 26 4 ...
Page 582: ...RATE LIMIT COMMANDS 27 6 ...
Page 616: ...SPANNING TREE COMMANDS 29 28 ...
Page 644: ...VLAN COMMANDS 30 28 ...
Page 664: ...CLASS OF SERVICE COMMANDS 31 20 ...
Page 678: ...QUALITY OF SERVICE COMMANDS 32 14 ...
Page 720: ...APPENDICES ...
Page 726: ...SOFTWARE SPECIFICATIONS A 6 ...
Page 730: ...TROUBLESHOOTING B 4 ...
Page 746: ...INDEX Index 6 ...
Page 747: ......