Tripp Lite B097016INT Owners Manual for B093- B097- and B098-Series Console Se - Page 255

on the server. Doing this ensures public key

Page 255 highlights

15. Advanced Configuration • Follow the instruction to move the mouse over the blank area of the program in order to create random data used by PUTTYGEN to generate secure keys. Key generation will occur once PUTTYGEN has collected sufficient random data. • Create a new file " authorized_keys " (with notepad) and copy your public key data from the "Public key for pasting into OpenSSH authorized_keys file" section of the PuTTY Key Generator. Paste the key data to the "authorized_keys" file. Make sure there is only one line of text in this file. • Use WinSCP to copy this "authorized_keys" file into the user's home directory. For example, /etc/config/users/testuser/. ssh/authorized_keys of the Tripp Lite gateway will be the SSH server. You will need to make sure this file is in the correct format with the correct permissions with the following commands: # dos2unix \ /etc/config/users/testuser/.ssh/authorized_keys && chown testuser \ /etc/config/users/testuser/.ssh/authorized_keys • Using WinSCP, copy the attached sshd_config over /etc/config/sshd_config on the server. Doing this ensures public key authentication is enabled. • Test the Public Key by logging in as "testuser". Test the Public Key by logging in as "testuser" to the client Tripp Lite device and typing (you should not need to enter anything): # ssh -o StrictHostKeyChecking=no To automate connection of the SSH tunnel from the client on every power-up, make the clients /etc/config/rc.local look like the following: #!/bin/sh ssh -L9001:127.0.0.1:4001 -N -o StrictHostKeyChecking=no testuser@ & This will run the tunnel redirecting local port 9001 to the server port 4001. 255

  • 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

255
15. Advanced Configuration
• Follow the instruction to move the mouse over the blank area of the program in order to create random data used by
PUTTYGEN to generate secure keys. Key generation will occur once PUTTYGEN has collected sufficient random data.
• Create a new file “
authorized_keys
“ (with notepad) and copy your public key data from the “Public key for pasting into
OpenSSH authorized_keys file” section of the PuTTY Key Generator. Paste the key data to the “authorized_keys” file. Make
sure there is only one line of text in this file.
• Use WinSCP to copy this “authorized_keys” file into the user’s home directory. For example,
/etc/config/users/testuser/.
ssh/authorized_keys
of the Tripp Lite gateway will be the SSH server. You will need to make sure this file is in the correct
format with the correct permissions with the following commands:
# dos2unix \
/etc/config/users/testuser/.ssh/authorized_keys && chown testuser \
/etc/config/users/testuser/.ssh/authorized_keys
• Using WinSCP, copy the attached sshd_config over
/etc/config/sshd_config
on the server. Doing this ensures public key
authentication is enabled.
• Test the Public Key by logging in as “testuser”. Test the Public Key by logging in as “testuser” to the client Tripp Lite device
and typing (you should not need to enter anything):
# ssh -o StrictHostKeyChecking=no <server-ip>
To automate connection of the SSH tunnel from the client on every power-up, make the clients /etc/config/rc.local look like the
following:
#!/bin/sh
ssh -L9001:127.0.0.1:4001 -N -o StrictHostKeyChecking=no testuser@<server-ip> &
This will run the tunnel redirecting local port 9001 to the server port 4001.