SSH Multiplexing ¶ Introduction ¶Īs previously mentioned, for security reasons, the CCI requires the TOTP authentication with each new connection, ruling out standard public-key authentication methods for remote access. There is, however, a way to create multiple connections using only one authentication. As such, generating and configuring these identity files is not documented here.
However, CCI systems require two-factor authentication with each new SSH connection and has disabled public-key authentication for off-site connections. Note: This SSH configuration file is also normally where you could supply specific public-key identity files for passwordless access. Typically, you'd connect to a landing pad through ssh with a command like: Let's say that your CCI username was EXPLname.
Let's create some host aliases for the CCI landing pads so that we can simplify our initial ssh command. Edit this file using a text editor of your choice. By default, your ssh configuration file for your profile on your local machine will likely be located at ~/.ssh/config. Different access parameters for each host can be independently specified here. This will start with the basic configuration to tell your SSH client about specific hosts (remote servers) that you connect to.
The core of this article will be based around configuring your SSH client to make your life simpler. If you are using a Windows system, we recommend the official "Windows Subsystem for Linux" (WSL2) provided by Microsoft to create a linux system kernel and environment within Windows.
Note: The following guide is for Linux/Unix based systems including Mac that use OpenSSH or a compatible ssh client.