Filter
Top Products
1101 and 1102 Secure Device Servers
724-746-5500 | blackbox.com
148
The key fingerprint is:
28:aa:29:38:ba:40:f4:11:5e:3f:d4:fa:e5:36:14:d6 user@server
$
Create a new directory to store your generated keys. You can also name the files after the device they will be used for. For example:
$ mkdir keys
$ ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/user/.ssh/id_rsa): /home/user/keys/control_room
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/user/keys/control_room
Your public key has been saved in /home/user/keys/control_room.pub.
The key fingerprint is:
28:aa:29:38:ba:40:f4:11:5e:3f:d4:fa:e5:36:14:d6 user@server
$
Make sure that there is no password associated with the keys. If there is a password, then the Black Box devices will have no way to supply it as
runtime.
Full documentation for the ssh-keygen command can be found at
$
#$!
For Black Box console servers, the keys can be simply uploaded through the web interface, on the System: Administration page. This enables you
to upload stored RSA or DSA Public Key pairs to the Master and apply the Authorized key to the slave and is described in Chapter 4. Once
complete, you then proceed to Fingerprinting as described below.
#$"
Alternately, the public key can be installed on the unit remotely from the linux host with the scp utility as follows.
Assuming the user on the Management Console is called "fred"; the IP address of the console server is 192.168.0.1 (default); and the public key is
on the linux/unix computer in ~/.ssh/id_dsa.pub. Execute the following command on the linux/unix computer:
scp ~/.ssh/id_dsa.pub \
# !"
The authorized_keys file on the console server needs to be owned by "fred", so login to the Management Console as root and type:
chown fred /etc/config/users/fred/.ssh/authorized_keys