Verifying a Secure Shell Connection (SSH)

When connecting using ssh for the first time to an unknown host (one of our remote access servers for example) you will be asked whether you trust this host with some kind of prompt similar to this one:

The authenticity of host 'SOMEHOST (N.N.N.N)' can't be established.
RSA key fingerprint is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Are you sure you want to continue connecting (yes/no)?

NOTE: Users using a newer version of OpenSSH will be using SHA256 as their default encryption method for viewing RSA fingerprints.  Our servers are still currently serving fingerprints as MD5.  What this means is that, one might ssh into a Courant access server and see a fingerprint beginning with "SHA256" which does not match below.  To view the fingerprints as we have published them here, add "-o FingerprintHash=md5" to your ssh command:

ssh -o FingerprintHash=md5 USERNAME@access.cims.nyu.edu

To verify the integrity of the host, make sure that the public key fingerprint matches those of our corresponding servers:

Hostname SSH RSA Fingerprint Last Updated
brawler.cims.nyu.edu 15:ed:cb:9e:ff:ae:3e:4f:41:e7:db:76:e6:6e:04:f7 2016/03/18
courses1.cs.nyu.edu 6f:9e:04:8f:8c:b7:71:d9:7e:49:34:d2:d8:f7:16:da 2016/03/18
courses2.cims.nyu.edu 6b:b5:d0:ae:2e:41:f3:ef:52:9f:68:e6:61:da:87:dd 2016/03/18
courses3.cims.nyu.edu bd:2f:a9:1d:67:e0:88:1d:bb:a2:97:4b:4e:cf:87:59 2016/03/18
crackle1.cims.nyu.edu da:64:d4:65:db:01:ce:9e:06:4d:8d:c8:a7:7c:71:54 2016/03/18
crackle2.cims.nyu.edu 73:a7:d7:f0:bd:ea:55:c5:df:f0:91:39:8f:fe:d5:ed 2016/03/18
crackle3.cims.nyu.edu 19:cc:55:25:cf:27:a3:9f:df:6d:86:ed:69:2c:0c:8a 2016/03/18
crackle4.cims.nyu.edu 5f:cf:79:de:bb:43:9a:9e:e3:25:21:48:f4:48:d6:ea 2016/03/18
crackle5.cims.nyu.edu 35:a1:cf:c0:88:30:a5:89:c7:d7:dd:a8:fe:f3:5e:ee 2016/03/18
crunchy1.cims.nyu.edu 38:4d:17:32:4c:f5:aa:b0:df:98:c7:ce:c9:94:55:53 2016/03/18
crunchy3.cims.nyu.edu ac:6c:1c:66:7d:4e:16:02:27:f5:1b:5f:bd:14:f9:37 2016/03/18
crunchy4.cims.nyu.edu 06:46:ef:f1:7f:ce:51:51:a2:b4:fa:04:8b:e1:7e:95 2016/03/18
crunchy5.cims.nyu.edu e9:33:a5:dc:4e:58:81:2a:cc:c1:a1:bb:15:c7:45:0d 2016/03/18
crunchy6.cims.nyu.edu 57:3e:b2:e2:6d:f4:e9:13:a0:f2:ed:56:8c:3a:01:4e 2016/03/18
crunchy12.cims.nyu.edu 21:f2:7d:69:53:ab:a8:52:22:6b:f3:9f:44:c8:2d:f0 2016/03/18
cuda1.cims.nyu.edu 09:94:a1:fb:5d:8b:f1:b1:8c:ca:3c:7e:01:a3:86:8b 2016/03/18
cuda2.cims.nyu.edu 52:7c:73:4a:7c:17:51:af:1d:a0:80:3a:4a:f5:d6:23 2016/03/18
cuda3.cims.nyu.edu f4:35:b7:5e:1b:f7:a8:1a:db:75:e4:1d:fc:cc:82:25 2016/03/18
cuda4.cims.nyu.edu 6f:0c:78:84:cd:1d:fe:bb:fd:49:fa:b4:74:95:d1:59 2016/03/18
cuda5.cims.nyu.edu dc:92:30:5b:06:f6:87:d8:35:7d:02:fc:63:51:4c:19 2016/03/18
energon1.cims.nyu.edu 97:73:96:0e:57:4f:c9:dc:8f:f0:70:c9:df:f0:1d:9d 2016/03/18
energon2.cims.nyu.edu bc:a1:53:ad:16:65:e5:96:fa:3f:3e:bf:75:58:5c:1c 2016/03/18
energon3.cims.nyu.edu 2d:f3:d1:55:93:47:d1:d0:87:23:f8:5d:24:29:53:1a 2016/03/18
energon4.cims.nyu.edu 21:06:d4:1f:da:55:70:5c:83:29:1d:60:d6:17:02:40 2016/03/18
euler01.cims.nyu.edu 2c:68:b1:18:85:25:db:40:54:2e:17:2a:3e:2e:a2:04 2016/03/18
i6.cims.nyu.edu 2c:68:b1:18:85:25:db:40:54:2e:17:2a:3e:2e:a2:04 2016/03/18
linax1.cims.nyu.edu 71:63:c0:cc:63:06:9b:6a:25:a1:17:62:48:be:3f:8f 2016/03/18
linax2.cims.nyu.edu 71:63:c0:cc:63:06:9b:6a:25:a1:17:62:48:be:3f:8f 2016/03/18
linserv1.cims.nyu.edu ed:d5:32:05:ce:48:a6:22:d5:28:ca:81:68:22:89:12 2016/03/18
linserv2.cims.nyu.edu 5f:cf:79:de:bb:43:9a:9e:e3:25:21:48:f4:48:d6:ea 2016/03/18
linserv3.cims.nyu.edu c4:81:77:4a:af:29:89:e0:b7:b2:a9:fb:17:58:f7:44 2016/03/18
mauler.cims.nyu.edu 38:d4:0a:6e:f0:a7:b9:02:78:01:f8:04:74:4b:9f:10 2016/03/18
opencl1.cims.nyu.edu ed:62:77:b0:42:86:13:b0:c3:86:d0:7e:3a:ae:03:c1 2016/03/18
opencl3.cims.nyu.edu 5f:cf:79:de:bb:43:9a:9e:e3:25:21:48:f4:48:d6:ea 2016/03/18

 

If the fingerprints provided do not match those listed above, you should immediately contact helpdesk@cims.nyu.edu.