This article describes a problem that may occur when you try to connect to a server using SSH, and how to resolve it.
When you try to connect to a server using SSH, you receive a warning message.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed.
If you are using PuTTY on Microsoft Windows, the message is:
WARNING - POTENTIAL SECURITY BREACH! The server's host key does not match the one PuTTY has cached in the registry. This means that either the server administrator has changed the host key, or you have actually connected to another computer pretending to be the server.
The most likely cause of this problem is that the RSA fingerprint has changed on the remote server, but the client computer still has the previous RSA fingerprint stored. This often occurs after you install a new operating system template on a server.
To resolve this problem, follow the appropriate procedure for your client computer's operating system.
To resolve this problem on client computers running Mac OS X or Linux, follow these steps:
Offending RSA key in /path/.ssh/known_hosts:x
When PuTTY displays the warning message, you have three options:
Subscribe to receive weekly cutting edge tips, strategies, and news you need to grow your web business.
No charge. Unsubscribe anytime.
Did you find this article helpful? Then you'll love our support. Experience the A2 Hosting difference today and get a pre-secured, pre-optimized website. Check out our web hosting plans today.
We use cookies to personalize the website for you and to analyze the use of our website. You consent to this by clicking on "I consent" or by continuing your use of this website. Further information about cookies can be found in our Privacy Policy.