Tripp Lite B0930082E4UV Owners Manual for B093- B097- and B098-Series Console - Page 251

Secure Shell SSH Public Key Authentication

Page 251 highlights

15. Advanced Configuration To set the SNMP Manager v3 Security Level field: config --set="config.system.snmp.seclevel3=noAuthNoPriv" or config --set="config.system.snmp.seclevel3=authNoPriv" or config --set="config.system.snmp.seclevel3=authPriv" To set the SNMP Manager v3 Username field: config --set="config.system.snmp.username3=username" To set the SNMP Manager v3 Auth. Protocol and password fields: config -set="config.system.snmp.authprotocol3=SHA" or config --set="config.system.snmp.authprotocol3=MD5" config --set="config.system.snmp.authpassword3=password 1" To set the SNMP Manager v3 Privacy Protocol and password fields: config -set="config.system.snmp.privprotocol3=AES" or config -set="config.system.snmp.privprotocol3=DES" config --set="config.system.snmp.privpassword3=password 2" Once the fields are set, apply the configuration with the following command: config --run snmp You can add a third or more SNMP servers by incrementing the "2" in the above commands (e.g., config.system.snmp. protocol3, config.system.snmp.address3, etc.). 15.6 Secure Shell (SSH) Public Key Authentication This section covers the generation of public and private keys in a Linux and Windows environment and configuring SSH for public key authentication. The steps to use in a clustering environment are: • Generate a new public and private key pair. • Upload the keys to the primary device and to each secondary console server. • Fingerprint each connection to validate. 15.6.1 SSH Overview Popular TCP/IP applications such as telnet, rlogin, ftp and others transmit their passwords unencrypted. Doing this across pubic networks like the Internet can have catastrophic consequences, as it allows an opening for eavesdropping, connection hijacking, and other network-level attacks. Secure Shell (SSH) is a program used to log into another computer over a network, execute commands in a remote machine and move files from one machine to another. It provides strong authentication and secure communications over insecure channels. OpenSSH, the de facto open source SSH application, encrypts all traffic (including passwords) to effectively eliminate these risks. Additionally, OpenSSH provides myriad secure tunneling capabilities, as well as a variety of authentication methods. OpenSSH is the port of OpenBSD's excellent OpenSSH[0] to Linux and other versions of UNIX. OpenSSH is based on the last free version of Tatu Ylonen's sample implementation, with all patent-encumbered algorithms removed (to external libraries), all known security bugs fixed, new features reintroduced and many other fixes. The only changes in the Tripp Lite SSH implementation are: • PAM support. • EGD[1]/PRNGD[2] support and replacements for OpenBSD library functions that are absent from other versions of UNIX. • The config files are now in /etc/config. e.g. o /etc/config/sshd_config instead of /etc/sshd_config o /etc/config/ssh_config instead of /etc/ssh_config o /etc/config/users//.ssh / instead of /home//.ssh/ 251

  • 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
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

251
15. Advanced Configuration
To set the SNMP Manager v3 Security Level field:
config --set=”config.system.snmp.seclevel3=noAuthNoPriv” or
config --set=”config.system.snmp.seclevel3=authNoPriv” or
config --set=”config.system.snmp.seclevel3=authPriv”
To set the SNMP Manager v3 Username field:
config --set=”config.system.snmp.username3=username”
To set the SNMP Manager v3 Auth. Protocol and password fields:
config –set=”config.system.snmp.authprotocol3=SHA” or
config --set=”config.system.snmp.authprotocol3=MD5”
config --set=”config.system.snmp.authpassword3=password 1”
To set the SNMP Manager v3 Privacy Protocol and password fields:
config –set=”config.system.snmp.privprotocol3=AES” or
config –set=”config.system.snmp.privprotocol3=DES”
config --set=”config.system.snmp.privpassword3=password 2”
Once the fields are set, apply the configuration with the following command:
config --run snmp
You can add a third or more SNMP servers by incrementing the “2” in the above commands (e.g., config.system.snmp.
protocol3, config.system.snmp.address3, etc.).
15.6 Secure Shell (SSH) Public Key Authentication
This section covers the generation of public and private keys in a Linux and Windows environment and configuring SSH for
public key authentication. The steps to use in a clustering environment are:
• Generate a new public and private key pair.
• Upload the keys to the primary device and to each secondary console server.
• Fingerprint each connection to validate.
15.6.1 SSH Overview
Popular TCP/IP applications such as telnet, rlogin, ftp and others transmit their passwords unencrypted. Doing this across
pubic networks like the Internet can have catastrophic consequences, as it allows an opening for eavesdropping, connection
hijacking, and other network-level attacks.
Secure Shell (SSH) is a program used to log into another computer over a network, execute commands in a remote machine
and move files from one machine to another. It provides strong authentication and secure communications over insecure
channels.
OpenSSH, the de facto open source SSH application, encrypts all traffic (including passwords) to effectively eliminate these
risks. Additionally, OpenSSH provides myriad secure tunneling capabilities, as well as a variety of authentication methods.
OpenSSH is the port of OpenBSD’s excellent OpenSSH[0] to Linux and other versions of UNIX. OpenSSH is based on the last
free version of Tatu Ylonen’s sample implementation, with all patent-encumbered algorithms removed (to external libraries),
all known security bugs fixed, new features reintroduced and many other fixes. The only changes in the Tripp Lite SSH
implementation are:
• PAM support.
• EGD[1]/PRNGD[2] support and replacements for OpenBSD library functions that are absent from other versions of UNIX.
• The config files are now in
/etc/config
. e.g.
o
/etc/config/sshd_config
instead of
/etc/sshd_config
o
/etc/config/ssh_config
instead of
/etc/ssh_config
o
/etc/config/users/<username>/.ssh /
instead of
/home/<username>/.ssh/