312
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
plant_entrance.pub
$ cat ~/keys/control_room.pub ~/keys/plant_entrance.pub > ~/keys/authorized_keys_bridge_server
Uploading keys
The keys for the server can be uploaded through the web interface, on the System > Administration page as detailed earlier. If
only one client will be connecting, then simply upload the appropriate public key as the authorized keys file. Otherwise, upload the
authorized keys file constructed in the previous step.
Each client will then need its own set of keys uploaded through the same page. Take care to ensure that the correct type of keys
(DSA or RSA) goes in the correct spots, and that the public and private keys are in the correct spot.
16.6.8 SDT CONNECTOR PUBLIC KEY AUTHENTICATION
SDT Connector can authenticate against a console server using your SSH key pair rather than requiring your to enter your password
(that is public key authentication).
To use public key authentication with SDT Connector, first create an RSA or DSA key pair (using ssh-keygen, PuTTYgen or a similar
tool) and add the public part of your SSH key pair to the console server.
Next, add the private part of your SSH key pair (this file is typically named id_rsa or id_dsa) to the SDT Connector client:
Navigate to Edit > Preferences > Private Keys > Add.
Locate the private key file.
Click OK.
You do not have to add the public part of your SSH key pair, it is calculated using the private key.
SDT Connector will now use public key authentication when SSH-connecting through the console server. You may have to restart
SDT Connector to shut down any existing tunnels that were established using password authentication.
If you have a host behind the console server that you connect to by clicking the SSH button in SDT Connector, you can also
configure it for public key authentication.
Essentially what you are using is SSH over SSH. The two SSH connections are entirely separate, and the host configuration is
entirely independent of SDT Connector and the console server. You must configure the SSH client that SDT Connector launches
(for example Putty or OpenSSH) and the host’s SSH server for public key authentication.
16.7 SECURE SOCKETS LAYER (SSL) SUPPORT
Secure Sockets Layer (SSL) is a protocol developed by Netscape for transmitting private documents via the Internet. SSL works by
using a private key to encrypt data that’s transferred over the SSL connection.
The console server includes OpenSSL. The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade,
full-featured, and Open Source toolkit implementing the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1)
protocols as well as a full-strength general purpose cryptography library. The project is managed by a worldwide community of
volunteers that use the Internet to communicate, plan, and develop the OpenSSL toolkit and its related documentation.
OpenSSL is based on the Slay library developed by Eric A Young and Tim J Hudson. The OpenSSL toolkit is licensed under an
Apache-style license, which basically means that you are free to get and use it for commercial and non-commercial purposes
subject to some simple license conditions. In the console server OpenSSL is used primarily in conjunction with https in order to
have secure browser access to the GUI management console across insecure networks.
OpenSSL documentation is available at https://openssl.org/docs/manmaster/apps/openssl.html.
