Revisions to How to remove strict RSA key checking in SSH and what's the problem here?

Add quote from article in OP's comments.

edit approved Aug 19, 2024 at 18:10

319
4
13

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Security focusFocus has a nice article on SSH host key protection.:

Why can a host key change? The machine to which you wish to connect has been moved to a different DNS name or IP address, or it's been replaced by a new one entirely.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Your connection might be getting dropped because of the StrictHostKeyCheckingStrictHostKeyChecking setting. See this thread for a similar issue.

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Security focus has a nice article on SSH host key protection.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Your connection might be getting dropped because of the StrictHostKeyChecking setting. See this thread for a similar issue.

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Security Focus has a nice article on SSH host key protection:

Why can a host key change? The machine to which you wish to connect has been moved to a different DNS name or IP address, or it's been replaced by a new one entirely.

Just remove the key (using SFTP or similar) from the server by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Your connection might be getting dropped because of the StrictHostKeyChecking setting. See this thread for a similar issue.

Revised to add more links and information.

Source Link

edited May 8, 2009 at 12:43

user1797

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Security focus has a nice article on SSH host key protection.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Your connection might be getting dropped because of the StrictHostKeyChecking setting. See this thread for a similar issue.

You are getting this because something has changed (like new NIC, new IP, change on server software, etc).

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Security focus has a nice article on SSH host key protection.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Your connection might be getting dropped because of the StrictHostKeyChecking setting. See this thread for a similar issue.

Clarified the possible reasons for the error.

Source Link

edited May 8, 2009 at 12:17

user1797

You are getting this because something has changed (like new NIC, new IP, change on server software, etc). Usually happens when your IP changes due a DHCP refresh.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

You are getting this because something has changed (like new NIC, new IP, etc). Usually happens when your IP changes due a DHCP refresh.

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

You are getting this because something has changed (like new NIC, new IP, change on server software, etc).

Just remove the key (using SFTP or similar) from the server, by editing the $HOME/.ssh/known_hosts file, and accept the new one upon next connection.

Source Link

answered May 8, 2009 at 11:41

user1797

Loading

Stack Exchange Network

Return to Answer