Configuring Secure Shell (SSH)
Overview
Overview
Feature | Default | Menu | CLI | Web |
Generating a public/private key pair on the switch | No | n/a | page | n/a |
Using the switch’s public key | n/a | n/a | page | n/a |
Enabling SSH | Disabled | n/a | page | n/a |
Enabling client | Disabled | n/a | pages | n/a |
|
|
|
| |
Enabling user authentication | Disabled | n/a | page | n/a |
|
|
|
|
|
The ProCurve switches covered in this guide use Secure Shell version 1 or 2 (SSHv1 or SSHv2) to provide remote access to management functions on the switches via encrypted paths between the switch and management station clients capable of SSH operation.
SSH provides
■Client
■Switch SSH and user password authentication
Client Public Key Authentication (Login/Operator Level) with UserPassword Authentication (Enable/Manager Level). This option uses one or more public keys (from clients) that must be stored on the switch. Only a client with a private key that matches a stored public key can gain access to the switch. (The same private key can be stored on one or more clients.)
ProCurve
Switch
(SSH
Server)
1.
options:
–Local
–TACACS+
–RADIUS
–None
SSH
Client
Work-
Station