1 Compute1 Basic Command
2 Compute2 Basic Command
3 Private-Public Key Pair
4 Updating Hosts for SSH Keys
5 SSH Multiplexing - Persistent Connection (Recommended for Compute2)

Compute1 Basic Command

ssh washkey@compute1-client-N.ris.wustl.edu

washukey is replaced by the user’s washukey.

N is replaced by 1, 2, 3, 4, or 5 as there are 5 login clients on Compute1.

Compute2 Basic Command

ssh washukey@c2-login-00N.ris.wustl.edu

washukey is replaced by the user’s washukey.

N is replaced by 1, 2, or 3 as there are 3 login clients on Compute2.

Private-Public Key Pair

SSH keys can be used to authenticate to the cluster. This is the recommended method and allows you to securely SSH to the compute client without entering a passphrase.

Generate key files ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub on your Linux/Unix/MacOS system, using the command ssh-keygen:

> ssh-keygen -f ~/.ssh/id_rsa
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /Users/${compute_username}/.ssh/id_rsa.
Your public key has been saved in /Users/${compute_username}/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:P10QiInCIHPUMeIiiP/wtOQwW1D6eItQ75o3pDn+vKk ${compute_username}@macbook.local
The key's randomart image is:
+---[RSA 2048]----+
|o.=++. . o ..    |
|o= ++.. o .  .   |
|= =  .      .    |
|.+ =         .   |
|. * B   S     .  |
| . /.o   . . .   |
|  o+B     o .    |
|  ++o.     .     |
| .E==o           |
+----[SHA256]-----+

It is recommended that you do not add a password to the ssh key. To do this when asked for a password/passphrase hit enter without typing anything else. You will need to do this for both prompts.

To avoid typing the passphrase for your key, use ssh-agent:

> eval `ssh-agent`
Agent pid 76698

Add your key to the agent:

> ssh-add ~/.ssh/id_rsa
Enter passphrase for /Users/${compute_username}/.ssh/id_rsa:

Now copy this SSH ID to the compute client:

> ssh-copy-id -i ~/.ssh/id_rsa washukey@c2-login-001.ris.wustl.edu
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/Users/washukey/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys


          ===========================================================
          ooooooooo.   ooooo  .oooooo..o        .oooooo.     .oooo.   
          `888   `Y88. `888' d8P'    `Y8       d8P'  `Y8b  .dP""Y88b  
           888   .d88'  888  Y88bo.           888                ]8P' 
           888ooo88P'   888   `"Y8888o.       888              .d8P'  
           888`88b.     888       `"Y88b      888            .dP'     
           888  `88b.   888  oo     .d8P      `88b    ooo  .oP     .o 
          o888o  o888o o888o 8""88888P'        `Y8bood8P'  8888888888 
          ===========================================================



You are connecting to RIS Compute services.
Membership in a compute-* AD group is required.

Users are responsible for acting in accordance with
policies applicable to Washington University St. Louis.

https://washu.atlassian.net/wiki/spaces/RUD/pages/2304737507/User+Agreements+and+Policies

(washukey@c2-login-001.ris.wustl.edu) Password: 
Autopushing login request to phone...
Success. Logging you in...
The system default contains no modules
  (env var: LMOD_SYSTEM_DEFAULT_MODULES is empty)
  No changes in loaded modules


Number of key(s) added:        1

Now try logging into the machine, with: "washukey@c2-login-001.ris.wustl.edu'"
and check to make sure that only the key(s) you wanted were added.

> ssh washukey@c2-login-001.ris.wustl.edu
Last login: Mon Oct 28 11:32:02 2019 from 10.23.317.459

> whoami
washukey

You are now able to securely SSH to the compute client without entering a passphrase.

Updating Hosts for SSH Keys

After Compute Platform maintenance it is recommended to update the SSH key host information. Users can do that with the following steps.

ssh-keygen

Run the following command
Compute1

ssh-keygen -R compute1-client-N.ris.wustl.edu

Compute2

ssh-keygen -R c2-login-00N.ris.wustl.edu

This safely removes all keys associated with that host.
This will need to be run for each login node for the Compute Platform.

SSH Multiplexing - Persistent Connection (Recommended for Compute2)

The following SSH connection setup uses the config file located in the user’s personal computer.
This allows for a persistent connection for a specified amount of time and makes it so that the 2FA required for Compute2 is only necessary once during the specified block of time.
- This makes it so that software like MobaXTerm and Visual Studio Code do not prompt the user for a 2FA push for every action.
The following should be added to a user’s config file in their .ssh folder on their personal computer.
- This is a hidden folder and user’s may need to make those visible in order to see it.
- On Mac: ~/.ssh/config
- On Windows: C:\Users\<YourUsername>\.ssh\config
Host c2-login-001 HostName c2-login-001.ris.wustl.edu ControlMaster auto ControlPath /tmp/ssh_mux_%h_%p_%r ControlPersist 8h User washukey Host c2-login-002 HostName c2-login-002.ris.wustl.edu ControlMaster auto ControlPath /tmp/ssh_mux_%h_%p_%r ControlPersist 8h User washukey Host c2-login-003 HostName c2-login-003.ris.wustl.edu ControlMaster auto ControlPath /tmp/ssh_mux_%h_%p_%r ControlPersist 8h User washukey

The Host can be named to what the user would like. The defaults included self identify the login host the user is utilizing.

washukey is replaced with the user’s WashU Key ID.

An entry in the file is needed for each login host.

To use one of these persistent connections, user’s can use the following command.

ssh c2-login-001

When connecting in this method, port forwarding will only work with the first connection attempt. Subsequent connection attempts involving port forwarding will fail.