Black Box LES1516A, User Manual

Page: 306 / 348

306
1.877.877.2269 BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
CHAPTER 16: ADVANCED CONFIGURATION
16.6.3 INSTALLING THE SSH PUBLIC & PRIVATE KEYS (CLUSTERING)
For console servers the keys can be uploaded through the web interface, on the System > Administration page.
FIGURE 16-3. SYSTEM > ADMINISTRATION SCREEN
This enables you to upload stored RSA or DSA Public Key pairs to the master and apply the authorized key to the slave as
documented in chapter 5. Once complete you then proceed to Fingerprinting as documented below.
16.6.4 INSTALLING THE SSH PUBLIC & PRIVATE KEYS (CLUSTERING)
Alternately, the public key can be installed on the unit remotely from the linux host with the scp utility.
Assumptions:
Š
Š
the Management Console username is fred.
Š
Š
the console server IP address is 192.168.0.1 (a console server’s default private IP address).
Š
Š
the public key is stored on the Linux- or UNIX-based system in ~/.ssh/id_dsa.pub.
Given this, run the following command from the Linux- or UNIX-based system:
scp ~/.ssh/id_dsa.pub \
root@192.168.0.1:/etc/config/users/fred/.ssh/authorized_keys
This copies the file to the console server but doesn’t set ownership as required. The authorized_keys file on the console server needs
to be owned by fred. To affect this, login to the Management Console as root and run the following command:
chown fred /etc/config/users/fred/.ssh/authorized_keys
If the console server selected to be the server has only one client device, the authorized_keys file is simply a copy of the public key for
that device.
If one or more devices will be clients of the console server, the authorized_keys file will contain copies of all of the public keys.
RSA and DSA keys may be freely mixed in the authorized_keys file. For example, assume we already have one server, called bridge_
server, and two sets of keys, for the control_room and the plant_entrance. The following commands 1) show the stored keys and 2)
combine two of them into a single file, authorized_keys_bridge_server.
$ ls /home/user/keys