|
|
| Line 1: |
Line 1: |
| <languages />
| |
|
| |
| Your SSH client will display the host key fingerprint the first time you try to connect to a server, or if it has no record of the server using that host key. When this happens you should always compare it to the published host key fingerprints for that server.
| |
|
| |
| Below are the host key fingerprints for Compute Canada servers, as of July 12, 2019.
| |
|
| |
|
| |
| == Béluga == | | == Béluga == |
| ; ECDSA | | ; ECDSA |
| Line 47: |
Line 40: |
| * <code>MD5:98:e7:7a:07:89:ef:3f:d8:68:3d:47:9c:6e:a6:71:5e</code> | | * <code>MD5:98:e7:7a:07:89:ef:3f:d8:68:3d:47:9c:6e:a6:71:5e</code> |
|
| |
|
| | | == ssh-test.computecanada.ca == |
| == SSH test node == | |
| We currently offer a test node that you can use to test your client of choice before the [[SSH changes|change happens]]. You can connect to it using the hostname <code>ssh-test.computecanada.ca</code> using your regular Compute Canada credentials. Its host key fingerprints are:
| |
| | |
|
| |
|
| ; ED25519 (256b) | | ; ED25519 (256b) |
| Line 58: |
Line 48: |
| : <code>SHA256:DMSia4nUKIyUhO5axZ/As4I8uqlaX0jPcJvcK93D2H0</code> | | : <code>SHA256:DMSia4nUKIyUhO5axZ/As4I8uqlaX0jPcJvcK93D2H0</code> |
| : <code>MD5:a7:08:00:7c:eb:81:f2:f7:2f:5a:92:b0:85:e3:e8:5d</code> | | : <code>MD5:a7:08:00:7c:eb:81:f2:f7:2f:5a:92:b0:85:e3:e8:5d</code> |
|
| |
|
| |
| If you can connect successfully to <code>ssh-test.computecanada.ca</code> now, then you will continue to be able to connect to our clusters when the SSH changes are made in the summer of 2019.
| |
|
| |
| == Another way to find host key fingerprints ==
| |
|
| |
| You can also determine the host key fingerprints for a server with the following commands:
| |
|
| |
| * for an MD5 fingerprint hash:
| |
| ssh-keyscan beluga.computecanada.ca | ssh-keygen -E md5 -l -f -
| |
|
| |
| * for an SHA256 fingerprint hash:
| |
| ssh-keyscan beluga.computecanada.ca | ssh-keygen -E sha256 -l -f -
| |