{"id":787,"date":"2017-10-24T15:09:37","date_gmt":"2017-10-24T15:09:37","guid":{"rendered":"http:\/\/ri.itservices.manchester.ac.uk\/icsf\/?page_id=787"},"modified":"2024-08-01T09:37:45","modified_gmt":"2024-08-01T09:37:45","slug":"hostkey","status":"publish","type":"page","link":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/getting-started-on-icsf\/connecting-to-incline\/hostkey\/","title":{"rendered":"Host Key Error on incline\/icsf Nodes"},"content":{"rendered":"<p>We have now taken the old 64GB &amp; 256GB nodes out of service. These were accessed via the addresses<\/p>\n<pre>incline.itservices.manchester.ac.uk\r\nicsf.itservices.manchester.ac.uk\r\n\r\nincline256.itservices.manchester.ac.uk\r\nicsf256.itservices.manchester.ac.uk\r\n<\/pre>\n<p>Those addresses are still valid but they will now log you into one of the incline2000 nodes.\u00a0\u00a0 This may cause you to see an error when logging in. See below on how to fix it:<\/p>\n<p>When logging in to one of the above addresses<\/p>\n<pre>ssh -X <em>username<\/em>@incline256.itservices.manchester.ac.uk\r\n     #\r\n     # (optional - the error may occur below with or without -X)\r\n<\/pre>\n<p>you may receive one or both the following errors about host identification:<\/p>\n<p><strong>PLEASE NOTE: incline.itservices.manchester.ac.uk &#8211; IP is 10.99.203.43 (change if appropriate) <\/strong><\/p>\n<pre>@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\r\n@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @\r\n@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\r\nThe RSA host key for incline256.itservices.manchester.ac.uk has changed,\r\nand the key for the corresponding IP address 10.99.203.70\r\nhas a different value. This could either mean that\r\nDNS SPOOFING is happening or the IP address for the host\r\nand its host key have changed at the same time.\r\nOffending key for IP in <strong>\/home\/<em>username<\/em>\/.ssh\/known_hosts:70<\/strong>\r\nremove with: <strong>ssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R 10.99.203.70<\/strong>\r\n                #\r\n                #\r\n                # If you see this message, follow the instructions: run\r\n                #\r\n                # <strong>ssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R 10.99.203.70<\/strong>\r\n                #\r\n                # (use the file path and username reported in your message!)\r\n\r\n@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\r\n@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @\r\n@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@\r\nIT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!\r\nSomeone could be eavesdropping on you right now (man-in-the-middle attack)!\r\nIt is also possible that a host key has just been changed.\r\nThe fingerprint for the RSA key sent by the remote host is\r\n<em>xx:xx:xx:xx:xx......:xx<\/em>.\r\nPlease contact your system administrator.\r\nAdd correct host key in \/home\/<em>username<\/em>\/.ssh\/known_hosts to get rid of this message.\r\nOffending RSA key in \/home\/<em>username<\/em>\/.ssh\/known_hosts:4\r\nremove with: <strong>ssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R incline256.itservices.manchester.ac.uk<\/strong>\r\nRSA host key for incline256.itservices.manchester.ac.uk has changed and you have requested strict checking.\r\nHost key verification failed.\r\n                #\r\n                #\r\n                # If you see this message, follow the instructions: run\r\n                #\r\n                # <strong>ssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R incline256.itservices.manchester.ac.uk<\/strong>\r\n                #\r\n                # (use the file path and username reported in your message!) \r\n\r\n<\/pre>\n<p>This occurs because incline256.itservices.manchester.ac.uk now defaults to using the incline2000 nodes which use a different host key.<\/p>\n<h3>Solutions<\/h3>\n<p>The easiest way to fix this if logging in from Linux (e.g., our X2GO desktop), or from MacOSX or in MobaXterm is to run the following command(s) in your terminal window (note: you will not be logged in to the iCSF at this point):<\/p>\n<p><strong>PLEASE NOTE: incline.itservices.manchester.ac.uk &#8211; IP is 10.99.203.43 (change if appropriate) <\/strong><\/p>\n<pre>ssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R 10.99.203.70\r\nssh-keygen -f \"\/home\/<em>username<\/em>\/.ssh\/known_hosts\" -R incline256.itservices.manchester.ac.uk\r\n                #                                           \r\n                #                                           \r\n                # \r\n                # Use the correct path and username reported in <em>your<\/em> error!\r\n<\/pre>\n<p>You should then log in using ssh:<\/p>\n<pre>ssh -X <em>username<\/em>@incline256.itservices.manchester.ac.uk\r\n<\/pre>\n<p>you will be asked to accept the new key:<\/p>\n<pre>The authenticity of host 'incline256.itservices.manchester.ac.uk (10.99.203.70)' can't be established.\r\nECDSA key fingerprint is <em>xx:xx:xx:xx:xx......:xx<\/em>.\r\nAre you sure you want to continue connecting (yes\/no)? <strong>yes<\/strong>\r\n                                                        #\r\n                                                        # Type <strong>yes<\/strong> and press Enter\r\n<\/pre>\n<p>It is <strong>safe<\/strong> to do so &#8211; answer <code>yes<\/code> at the prompt. You will then be logged in to one of the 2TB compute nodes.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We have now taken the old 64GB &amp; 256GB nodes out of service. These were accessed via the addresses incline.itservices.manchester.ac.uk icsf.itservices.manchester.ac.uk incline256.itservices.manchester.ac.uk icsf256.itservices.manchester.ac.uk Those addresses are still valid but they will now log you into one of the incline2000 nodes.\u00a0\u00a0 This may cause you to see an error when logging in. See below on how to fix it: When logging in to one of the above addresses ssh -X &#x75;s&#x65;&#114;&#x6e;&#x61;m&#x65;&#64;&#x69;&#x6e;c&#x6c;&#105;&#x6e;&#x65;2&#x35;&#54;&#x2e;&#x69;t&#x73;&#101;&#x72;&#x76;i&#x63;&#101;&#x73;&#x2e;m&#x61;&#110;&#x63;&#x68;e&#x73;&#116;&#x65;&#x72;&#46;&#x61;&#99;&#x2e;&#x75;k # # (optional &#8211; the.. <a href=\"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/getting-started-on-icsf\/connecting-to-incline\/hostkey\/\">Read more &raquo;<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"parent":64,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-787","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/pages\/787","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/comments?post=787"}],"version-history":[{"count":21,"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/pages\/787\/revisions"}],"predecessor-version":[{"id":1387,"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/pages\/787\/revisions\/1387"}],"up":[{"embeddable":true,"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/pages\/64"}],"wp:attachment":[{"href":"https:\/\/ri.itservices.manchester.ac.uk\/icsf\/wp-json\/wp\/v2\/media?parent=787"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}