SSH

Table of Contents:

Login Nodes

The following machines can be used for remote SSH access to SLAC:

Example usage:

ssh centos7.slac.stanford.edu

You can add your username to the login command like this:

ssh centos7.slac.stanford.edu -l username

(replace "username" with your actual SLAC username.

X11 GUI access

SSH is capable of forwarding X11 through the connection. This will be slow when you are connecting from a non-SLAC network. To display SLAC X11 / GUI applications to your remote desktop or laptop, we have FastX available. For more information, see https://confluence.slac.stanford.edu/display/SCSPub/FastX and https://www.starnet.com/fastx/ .

FastX works for LAN or WAN access, and is optimized for Remote Linux X Windows, and can be used if the default SSH X11 tunneling does not provide adequate performance.

Data Transfer Nodes (DTN)

ssh and scp are not the most optimized tool for large data transfers. bbcp and/or globus are better choices. There are two Data Transfer Nodes available for this:

dtn01.slac.stanford.edu
dtn02.slac.stanford.edu

For more information, see https://confluence.slac.stanford.edu/display/SCSPub/Transferring+Data .

SSH between a non-SLAC machine and a SLAC machine

If you have an AFS home directory on your SLAC linux computer, using ssh host keys will not be very useful since that will not provide you with an AFS token. Instead of ssh host keys, you can use Kerberos (GSSAPI) Authentication by doing the following:

1. Turn on GSSAPI options in your ~/.ssh/config file.

   # Specifies whether user authentication based on GSSAPI is allowed.
   GSSAPIAuthentication yes
   
   # Forward (delegate) credentials to the server.                   
   GSSAPIDelegateCredentials yes