- Follow the steps outlined under Using Public Keys with SSH to create your key.
- Copy the public key (
id_dsa.pub) to a file named
yourUserId.pub-- for example, if your chosen user ID is "jldoe", save the key in the file
jdoe.pubusing a command such as:
cp ~/.ssh/id_rsa.pub jdoe.pub
- Attach that file to an e-mail message and send it to firstname.lastname@example.org with the subject line "SPO600 Key".
An account will be created within a few work days of sending the key.
An AArch64 system is available, known as "aarchie". You can access this system at the hostname aarchie.cdot.systems; if you're using a command-line ssh system, you can access aarchie with a command such as this:
The x86_64 server system is known as xerxes. If you're using a command-line ssh system, you can access xerxes with a command such as this:
Simplified SSH Access
If you're using OpenSSH (the ssh client used on most Linux systems and other platforms), you can simplify ssh command lines by placing host connection details in the file
Host "aarchie" hostname "aarchie.cdot.systems" user "YourUserID" Host "xerxes" hostname "xerxes.cdot.systems" user "YourUserID"
Once you have added these lines (inserting your user ID where appropriate) and set the permission on that file (
chmod 0600 ~/.ssh/config) you can use these commands to access the servers:
ssh aarchie ssh xerxes
You can similarly configure simplified access in most other SSH client programs.
SSH Access from Other Client Systems
If you wish to access the servers from additional computers, you can append the SSH public keys from those computers to the
To perform operations which require privilege, such as installing software, use the
sudo command to execute the desired instruction as the
For example, to install the software packaged
sudo dnf install ncurses-devel on xerxes or
sudo yum install ncurses-devel on betty. The commands are different because Xerxes is running Fedora, which has transitioned from the older yum system to dnf, while Betty is running LEAP (based on CentOS), which still uses the older system.
In order to use
sudo, you will need to know your password. An initial random password is provided in the file
~/password.txt (note that your password will be different on each server). Feel free to change this with the
passwd command -- not by editing the file, which is provided only for your information!
Remember that these machines are multi-user systems. Use the
who commands to see who else is using them; you can also try using the
write command to communicate with another user if required.
Backup Your Accounts
These accounts are never backed up, and the machines may fail, lose data, or be reinstalled without warning at any time. Please back up your work frequently by copying it to another system or storage device.
Common SSH Problems
With the OpenSSH client:
- Your ssh private key must be in your
~/.sshdirectory (which must have 0700 permission) and the private key file must have 0600 permissions -- no more and no less.
- If your SSH public key is not named
~/.ssh/id_rsa, your SSH client may not automatically find it. You can specify the identity (private key) file using the
-iargument to the SSH command.}}
With other SSH clients:
- Your key must be in OpenSSH format when you send it to your professor; this format is used by the default SSH client on Mac OS/X and Linux as well as PuTTY. If it is in SSH2 format, used by some other client programs, you can convert it with this command on a Linux system with OpenSSH (such as Matrix):
ssh-keygen -i -f ~/.ssh/SSH2_PUBLIC_KEY_FILE.pub > ~/.ssh/OPENSSH_PUBLIC_KEY_FILE.pub
The screen utility provides disconnect/reconnect capability, which is very useful for unstable network connections, long interactive operations, and changing your work location.