This walk-through presumes that the user

  • is working on a Linux machine, a mac or a windows machine with openssh installed (default on recent Windows 10+ versions)

  • has OpenSSH installed: ssh -V in the terminal to check

  • has an account on the server of interest

  • is connected to the Aalto network

We will be focusing on connecting to Triton but the methods described below are applicable to any of Aalto’s other remote servers.

Basic use: connect to a server

The standard login command is ssh login_name@host_name, where login_name is your standard Aalto login and host_name is the address of the server you with to connect. In the case of Triton, the host_name is

First time login

For Triton, you will be prompted to affirm that you wish to ssh into this server for the first time.

The authenticity of host ' (' can't be established.
ECDSA key fingerprint is SHA256:04Wt813WFsYjZ7KiAyo3u6RiGBelq1R19oJd2GXIAho.
Are you sure you want to continue connecting (yes/no)?

Compare the key fingerprint you get to the one for the machine at this Triton ssh key fingerprints, and if they do not match, please contact SciComp IT immediately. If they do match, type yes and press enter. You will receive a notice

Warning: Permanently added ',' (ECDSA) to the list of known hosts.

The public key that identifies Triton will be stored in ~/.ssh/known_hosts and you ought not get this prompt again. You will be also asked to input your Aalto password before you are fully logged in.

Known servers

You will not receive an authenticity prompt upon first login if the server’s public key can be found in a list of known hosts. To check whether a server, Kosh for example, is known

ssh-keygen -f %USERPROFILE%\.ssh\known_hosts -F

SSH keys: better than just passwords

By default, you will need to type your password each time you wish to ssh into Triton, which can be tiresome, particularly if you regularly have multiple sessions open simultaneously. A more secure (and faster) way to authenticate yourself is to use a SSH key pair and encrypt the this with a strong password. xkcd has good and amusing recommendations on the subject of passwords. This authentication method will allow you to log into multiple ssh sessions while only needing to enter your password once, saving you time and keystrokes.

Generate an SSH key

While there are many options for the key generation program ssh-keygen, here are the four main ones.

  • -t -> the cryptosystem used to make the unique key-pair and encrypt it.

  • -b -> the number of key bits

  • -f -> filename of key

  • -C -> comment on what the key is for

Here are our recommended input options for key generation.

ssh-keygen -t rsa -b 4096 -f %USERPROFILE%\.ssh\id_rsa_triton -C "triton key for %USERNAME%"

After running this command in the terminal, you will be prompted to enter a password. PLEASE use a strong unique password. Upon confirming the password, you will be presented with the key fingerprint as both a SHA256 hex string as well as randomart image. Your new key pair should be found in the hidden ~/.ssh directory. If you wish to use keys for other servers, you should generate new key pairs and use different passwords.

Copy public key to server

In order to use your key-pair to login to Triton, you first need to securely copy the desired public key to the machine with ssh-copy-id. The script will also add the key to the ~/.ssh/authorized_keys file on the server. You will be prompted to enter your Aalto password to initiate the secure copy of the file to Triton.


Connecting from outside of the aalto network

The following command works, if you are within the Aalto network or if you are connected via vpn. If you log in from outside Aalto, you first need to set up the key for the login server (e.g. kosh). This can be done by replacing by in the following command. If you connect from outside aalto it is useful to first set up the config file as described below. Once this is done run the following command once with kosh instead of followed by the same command with triton_via_kosh instead of to transfer your public keys to both the firewall server kosh and triton.

type %USERPROFILE%\.ssh\ | ssh "cat >> .ssh/authorized_keys"

Login with SSH key

To avoid having to type the decryption password, the private key needs to be added to the ssh-agent with the command

You will need administrative permissions to be able to start a ssh-agent on your machine that can store and handle passwords.

  1. Open Services from the start menu

  2. Scroll down to OpenSSH Authentication Agent > double click

  3. Change the Startup type to Automatic (Delayed Start), or anything that is not Disabled and also start the service manually if it is not yet running

  4. ssh-add %USERPROFILE%\.ssh\id_rsa_triton

Once the password is added, you can ssh into Triton as normal but will immediately be connected without any further prompts.


Often, you can’t connect directly to your target computer: you need to go through some other firewall host. This is often done with two separate ssh commands, but can be done with only one with the -J (ProxyJump) option:

ssh -J

Both of these can take more options, for example if you need to specify your username you might need to do it twice:

ssh -J

Read more details at, including putting this in your configuration file (or see below).

Config file: don’t type so many options

Remembering the full settings list for the server you are working on each time you log in can be tedious. A ssh config file allows you to store your preferred settings and map them to much simpler login commands. To create a new user-restricted config file

copy NUL %USERPROFILE%\.ssh\config

Open the created file to edit it as indicated below.

For a new configuration, you need specify in config at minimum the

  • Host: the name of the settings list

  • User: your login name when connecting to the server

  • Hostname: the address of the server

So for the simple Triton example, it would be:

# Configuration file for simplifying SSH logins
# HPC slurm cluster
Host triton

and you would use ssh triton to log in. Any additional server configs can follow the first one and must start with declaring the configuration Host:

# general login server
Host kosh
# light-computing server
Host brute

There are optional ssh settings that may be useful for your work, such as:

# Turn on X11 forwarding for Xterm graphics access
ForwardX11 yes
# Connect through another server (eg Kosh) if not connected directly to Aalto network
# Specify which ssh private key is used for login identification
IdentityFile ~/.ssh/id_rsa_triton

Full sample config file

The following code is placed in the config file created above (i.e. ~/.ssh/config on mac/linux or %USERPROFILE%.ssh/config on windows)

# general login server
Host kosh
    IdentityFile ~/.ssh/id_rsa_triton

# Triton, via kosh
Host triton_via_kosh
    ProxyJump kosh
    IdentityFile ~/.ssh/id_rsa_triton

Now, you can just do ssh triton or rsync triton:/m/cs/scratch/some_file . directly, by using the triton alias. Note that the Triton rule uses the name kosh which is defined in the first part of the file. The IdentityFile parameter is necessary only if you have a non-default key name (like the one indicated).