HP 6120G/XG HP ProCurve Series 6120 Blade Switches IPv6 Configuration Guide - Page 140

Secure Shell (SSH) for IPv6, Configuring SSH for IPv6

Page 140 highlights

IPv6 Management Security Features Secure Shell (SSH) for IPv6 Secure Shell (SSH) for IPv6 SSH for IPv4 and IPv6 operate simultaneously with the same command set. Both are enabled in the default configuration, and are controlled together by the same command set. Secure Shell (SSH) for IPv6 provides the same Telnet-like functions through encrypted, authenticated transactions as SSH for IPv4. SSH for IPv6 provides CLI (console) access and secure file transfer functionality. The following types of transactions are supported: ■ Client public-key authentication Public keys from SSH clients are stored on the switch. Access to the switch is granted only to a client whose private key matches a stored public key. ■ Password-only client authentication The switch is SSH-enabled but is not configured with the login method that authenticates a client's public-key. Instead, after the switch authenticates itself to a client, users connected to the client authenticate themselves to the switch by providing a valid password that matches the operator- and/or manager-level password configured and stored locally on the switch or on a RADIUS or TACACS+ server. ■ Secure Copy (SCP) and Secure FTP (SFTP) client applications You can use either one SCP session or one SFTP session at a given time to perform secure file transfers to and from the switch. Configuring SSH for IPv6 By default, SSH is automatically enabled for IPv4 and IPv6 connections on a switch. You can use the ip ssh command options to reconfigure the default SSH settings to configure the following settings used in SSH authentication for IPv4 and IPv6 connections: ■ TCP port number ■ timeout period ■ file transfer ■ MAC type ■ cipher type 6-15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167

6-15
IPv6 Management Security Features
Secure Shell (SSH) for IPv6
Secure Shell (SSH) for IPv6
SSH for IPv4 and IPv6 operate simultaneously with the same command set.
Both are enabled in the default configuration, and are controlled together by
the same command set.
Secure Shell (SSH) for IPv6 provides the same Telnet-like functions through
encrypted, authenticated transactions as SSH for IPv4. SSH for IPv6 provides
CLI (console) access and secure file transfer functionality. The following types
of transactions are supported:
Client public-key authentication
Public keys from SSH clients are stored on the switch. Access to the
switch is granted only to a client whose private key matches a stored
public key.
Password-only client authentication
The switch is SSH-enabled but is not configured with the login method
that authenticates a client’s public-key. Instead, after the switch authenti-
cates itself to a client, users connected to the client authenticate them-
selves to the switch by providing a valid password that matches the
operator- and/or manager-level password configured and stored locally on
the switch or on a RADIUS or TACACS+ server.
Secure Copy (SCP) and Secure FTP (SFTP) client applications
You can use either one SCP session or one SFTP session at a given time
to perform secure file transfers to and from the switch.
Configuring SSH for IPv6
By default, SSH is automatically enabled for IPv4 and IPv6 connections on a
switch. You can use the
ip ssh
command options to reconfigure the default
SSH settings to configure the following settings used in SSH authentication
for IPv4 and IPv6 connections:
TCP port number
timeout period
file transfer
MAC type
cipher type