HP 6125XLG R2306-HP 6125XLG Blade Switch Security Configuration Guide - Page 140

Configuration procedure, Setting the SSH management parameters

Page 140 highlights

• For an SFTP or SCP user, the working directory depends on the authentication method: { If the authentication method is password, the working directory is authorized by AAA. { If the authentication method is publickey or password-publickey, the working folder is specified by the authorization-attribute command in the associated local user view. • For an SSH user, the user role also depends on the authentication method: { If the authentication method is password, the user role is authorized by the remote AAA server or the local device. { If the authentication method is publickey or password-publickey, the user role is specified by the authorization-attribute command in the associated local user view. • If you change the authentication method or public key for an SSH user that has been logged in, the change can take effect only at the next login of the user. • Except password authentication, the other authentication methods require a client's host public key to be specified. For more information about host public keys, see "Configuring a client's host public key." • When the device operates in FIPS mode as an SSH server, the device does not support the authentication method of any or publickey. For information about configuring local users and remote authentication, see "Configuring AAA." Configuration procedure To configure an SSH user, and specify the service type and authentication method: Step 1. Enter system view. 2. Create an SSH user, and specify the service type and authentication method. Command system-view • In non-FIPS mode: ssh user username service-type { all | scp | sftp | stelnet } authentication-type { password | { any | password-publickey | publickey } assign publickey keyname } • In FIPS mode: ssh user username service-type { all | scp | sftp | stelnet } authentication-type { password | password-publickey assign publickey keyname } Setting the SSH management parameters Setting the SSH management parameters can improve the security of SSH connections. The SSH management parameters include: • Whether the SSH server is compatible with SSH1 clients. • RSA server key pair update interval, applicable to users using SSH1 clients. • SSH user authentication timeout period. You can set this parameter to reject a connection if the authentication for the connection has not been finished when the timeout period expires. • Maximum number of SSH authentication attempts. You can set this parameter to prevent malicious password cracking. If the authentication method is any, the total number of both publickey and password authentication attempts cannot exceed the configured upper limit. • ACL for SSH clients. You can configure an ACL to filter SSH clients which initiate connections with the SSH server. 131

  • 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
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276

131
For an SFTP or SCP user, the working directory depends on the authentication method:
{
If the authentication method is
password
, the working directory is authorized by AAA.
{
If the authentication method is
publickey
or
password-publickey
, the working folder is specified
by the
authorization-attribute
command in the associated local user view.
For an SSH user, the user role also depends on the authentication method:
{
If the authentication method is
password
, the user role is authorized by the remote AAA server
or the local device.
{
If the authentication method is
publickey
or
password-publickey
, the user role is specified by
the
authorization-attribute
command in the associated local user view.
If you change the authentication method or public key for an SSH user that has been logged in, the
change can take effect only at the next login of the user.
Except password authentication, the other authentication methods require a client's host public key
to be specified. For more information about host public keys, see "
Configuring a client's host public
key
."
When the device operates in FIPS mode as an SSH server, the device does not support the
authentication method of
any
or
publickey
.
For information about configuring local users and remote authentication, see "
Configuring AAA
."
Configuration procedure
To configure an SSH user, and specify the service type and authentication method:
Step
Command
1.
Enter system view.
system-view
2.
Create an SSH user, and
specify the service type and
authentication method.
In non-FIPS mode:
ssh user
username
service-type
{
all
|
scp
|
sftp
|
stelnet
}
authentication-type
{
password
| {
any
|
password-publickey
|
publickey
}
assign publickey
keyname
}
In FIPS mode:
ssh user
username
service-type
{
all
|
scp
|
sftp
|
stelnet
}
authentication-type
{
password
|
password-publickey assign
publickey
keyname
}
Setting the SSH management parameters
Setting the SSH management parameters can improve the security of SSH connections. The SSH
management parameters include:
Whether the SSH server is compatible with SSH1 clients.
RSA server key pair update interval, applicable to users using SSH1 clients.
SSH user authentication timeout period. You can set this parameter to reject a connection if the
authentication for the connection has not been finished when the timeout period expires.
Maximum number of SSH authentication attempts. You can set this parameter to prevent malicious
password cracking. If the authentication method is
any
, the total number of both publickey and
password authentication attempts cannot exceed the configured upper limit.
ACL for SSH clients. You can configure an ACL to filter SSH clients which initiate connections with
the SSH server.