User`s manual

_____________________________________________________________________
724-746-5500 | blackbox.com Page 207
authorized_keys file is simply a copy of the public key for that device. If one or more devices will be
clients of the server, then the authorized_keys file will contain a copy 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:
$ ls /home/user/keys control_room control_room.pub plant_entrance plant_entrance.pub $ cat
/home/user/keys/control_room.pub /home/user/keys/plant_entrance.pub >
/home/user/keys/authorized_keys_bridge_server
More documentation on OpenSSH can be found at:
http://openssh.org/portable.html
http://www.openbsd.org/cgi-bin/man.cgi?query=ssh&sektion=1
http://www openbsd.org/cgi-bin/man.cgi?query=sshd.
15.6.5 Generating public/private keys for SSH (Windows)
This section describes how to generate and configure SSH keys using Windows.
First create a new user from the Black Box Management (the following example uses a user called
"testuser") making sure it is a member of the "users" group.
If you do not already have a public/private key pair you can generate them now using ssh-keygen,
PuTTYgen or a similar tool:
PuTTYgen: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
----BEGIN DSA
PRIVATE KEY----
MIIBugIBAAKBgQCR
kixjJOSKuiEXTM
x0PFp9HqBvEg7Ww9
oynY4QNIXj1YU7T
87IFLQiAhn3yp7ZWy
7Z5C4sLF8o46Go
----BEGIN DSA
PRIVATE KEY----
MIIEogIBAAKCAQEA
yIPGsNf5+a0LnPUMc
nujXXPGiQGyD3b79
KZg3UZ4MjZI525sCy
opv4TJTvTK6e8QIYt
GYTByUdI
ssh-dss
AAAAB3NzaZr+OV01C8gdgz
XDg==name@client2
ssh-rsa
AAAAB3NzaC1yc2Efg4+tG
HIAAA==name@client1
ssh-rsa AAAB3NzaC1yc2Efg4+GHI
AAA=name@client1
ssh-dss AAAAB3NzaZr+OV01C8gdgz
xDg==name@client2
Master Master
Slave
id_dsa
id_dsa.pub id_rsa.pub
id_rsa
authoriz ed_keys