You are here
External login (ssh) servers
This page is about our two SSH gateways - student.ssh.inf.ed.ac.uk for all users and staff.ssh.inf.ed.ac.uk for staff, research postgraduates and visitors. The Informatics computer network is protected by a firewall so any login from outside that network has to use either an SSH gateway or OpenVPN or NX.
General information about using School services from outside can be found in the remote working page.
For platform-specific advice; follow the links below:
Please note: these servers are just gateways to other DICE servers. To improve security they only have a small set of installed software. If a process uses too much of the ssh server's resources it will have to be killed to keep the server working for all users. Please avoid accessing these servers from machines that you can not trust (e.g. those not running anti-virus software; public machines in another institution). Ideally, use a Kerberos-authenticated SSH connection. You should regularly review your login activity to ensure that your account has not become compromised. If your ssh connection from home seems to time out and disconnect quickly, see ssh timeouts from home for a solution. If an ssh login attempt fails with the message
ssh_exchange_identification: read: Connection reset by peer then see this advice page.
There are two SSH servers, they are:
|Host||IP Address||Key Fingerprint||Service Name(s)||Access|
||ssh.inf.ed.ac.uk and student.ssh.inf.ed.ac.uk
||staff.ssh.inf.ed.ac.uk||Staff, research postgraduates and visitors|
Both servers are running ScientificLinux version 7 which is based on Redhat Enterprise Linux (RHEL).
In theory the use of ssh public key authentication is much more secure than using passwords, especially in that it effectively prevents "brute force" style attacks. However, there are a number of issues which have led to us taking the decision to block all authentication using ssh public keys.
The main issue with ssh public key authentication is that it does not fit well with our use of AFS for home directories. Access to an AFS home directory requires the acquisition of a Kerberos ticket, this will not occur automatically when a user authenticates using a public key (but does when using a password or GSSAPI authentication). This would lead to the user having to authenticate with a password immediately after having authenticated with a public key which is confusing and negates the main reasons for using a public key.
A secondary issue is the management of the private key. If the file containing the private key is not kept secure then it can be used to gain unauthorised access to systems which hold the public key. There is the option to set a pass phrase on the private key file but not all users do this and there is no way for that to be mandated. This reduces the security of the systems holding the public key to the level of that holding the private key. The worst aspect though is that the private key can be easily copied onto many separate hosts with varying levels of security. A number of high profile organisations have suffered intrusions because of this problem.
Most people who use public keys appreciate being able to make use of the "single sign on" that it offers when used in conjunction with an ssh key agent. This means that a user only has to enter a pass phrase once to access the private key and from then on they can make as many connections as necessary without having to manually authenticate. In Informatics we use Kerberos for authentication and this provides the ability to do true "single sign on". Using GSSAPI authentication (i.e. Kerberos) is the most secure way to access the Informatics ssh service and also the most convenient once a small amount of configuration has been done on your system. Further details on how to configure your system to use Kerberos can be found elsewhere on this site.