Lantronix SLC 32 Lantronix SLC - User Guide - Page 168

SSH Keys, Imported Keys

Page 168 highlights

12: User Authentication SSH Keys The SLC console manager can import and export SSH keys to facilitate shared key authentication for all incoming and outgoing SSH connections. By using a public/private key pair, a user can access multiple hosts with a single passphrase, or, if a passphrase is not used, a user can access multiple hosts without entering a password. In either case, the authentication is protected against security attacks because both the public key and the private key are required to authenticate. For both imported and exported SSH keys, the SLC device supports both RSA and DSA keys, and can import and export keys in OpenSSH and SECSH formats. Imported and exported keys are saved with the SLC configuration, and the administrator has the option of retaining the SSH keys during a reset to factory defaults. The SLC console manager can also update the SSH RSA1, RSA and DSA host keys that the SSH server uses with site-specific host keys or reset them to the default values. Imported Keys Imported SSH keys must be associated with an SLC local user. The key can be generated on host "MyHost" for user "MyUser," and when the key is imported into the SLC unit, it must be associated with either "MyUser" (if "MyUser" is an existing SLC local user) or an alternate SLC local user. The public key file can be imported via SCP or FTP; once imported, you can view or delete the public key. Any SSH connection into the SLC console manager from the designated host/user combination uses the SSH key for authentication. Exported Keys The SLC device can generate SSH keys for SSH connections out of the SLC console manager for any SLC user. The SLC unit retains both the private and public key on the SLC console manager, and makes the public key available for export via SCP, FTP, or copy and paste. The name of the key is used to generate the name of the public key file that is exported (for example, .pub), and the exported keys are organized by user and key name. Once a key is generated and exported, you can delete the key or view the public portion. Any SSH connection out of the SLC device for the designated host/user combination uses the SSH key for authentication. SLC™ Console Manager User Guide 168

  • 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
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299

12: User Authentication
SLC™ Console Manager User Guide
168
SSH Keys
The SLC console manager can import and export SSH keys to facilitate shared key authentication
for all incoming and outgoing SSH connections. By using a public/private key pair, a user can
access multiple hosts with a single passphrase, or, if a passphrase is not used, a user can access
multiple hosts without entering a password. In either case, the authentication is protected against
security attacks because both the public key and the private key are required to authenticate.
For both imported and exported SSH keys, the SLC device supports both RSA and DSA keys, and
can import and export keys in OpenSSH and SECSH formats. Imported and exported keys are
saved with the SLC configuration, and the administrator has the option of retaining the SSH keys
during a reset to factory defaults.
The SLC console manager can also update the SSH RSA1, RSA and DSA host keys that the SSH
server uses with site-specific host keys or reset them to the default values.
Imported Keys
Imported SSH keys must be associated with an SLC local user. The key can be generated on host
“MyHost” for user “MyUser,” and when the key is imported into the SLC unit, it must be associated
with either “MyUser” (if “MyUser” is an existing SLC local user) or an alternate SLC local user.
The public key file can be imported via SCP or FTP; once imported, you can view or delete the
public key. Any SSH connection into the SLC console manager from the designated host/user
combination uses the SSH key for authentication.
Exported Keys
The SLC device can generate SSH keys for SSH connections out of the SLC console manager for
any SLC user. The SLC unit retains both the private and public key on the SLC console manager,
and makes the public key available for export via SCP, FTP, or copy and paste. The name of the
key is used to generate the name of the public key file that is exported (for example,
<keyname>.pub), and the exported keys are organized by user and key name. Once a key is
generated and exported, you can delete the key or view the public portion. Any SSH connection
out of the SLC device for the designated host/user combination uses the SSH key for
authentication.