Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[CODE]ssh root@192.168.1.1 -p ######
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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.
The fingerprint for the RSA key sent by the remote host is
SHA256:Sa0f8v+L1FUvN0t0/cVPkuV6XIShgZirngrPhm53ias.
Please contact your system administrator.
Add correct host key in /Users/userr/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/user/.ssh/known_hosts:3
RSA host key for [192.168.1.1]####### has changed and you have requested strict checking.
Host key verification failed.
raf:.ssh rafbancer$ nanao known_hosts
-bash: nanao: command not found
raf:.ssh user$ ls
id_ed25519 id_ed25519.pub id_rsa id_rsa.pub known_hosts
raf:.ssh user$ nano known_hosts[/CODE}
What I did was I reinstalled router ( Linksys WRT 3200 ACM ) firmware and wanted to add my ssh info and thats what the terminal spit out. What can I do? Please I will answer anything.
ssh root@192.168.1.1 -p ######
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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.
The fingerprint for the RSA key sent by the remote host is
SHA256:Sa0f8v+L1FUvN0t0/cVPkuV6XIShgZirngrPhm53ias.
Please contact your system administrator.
Add correct host key in /Users/userr/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/user/.ssh/known_hosts:3
RSA host key for [192.168.1.1]####### has changed and you have requested strict checking.
Host key verification failed.
raf:.ssh rafbancer$ nanao known_hosts
-bash: nanao: command not found
raf:.ssh user$ ls
id_ed25519 id_ed25519.pub id_rsa id_rsa.pub known_hosts
raf:.ssh user$ nano known_hosts
What I did was I reinstalled router ( Linksys WRT 3200 ACM ) firmware and wanted to add my ssh info and thats what the terminal spit out. What can I do? Please I will answer anything.
Remove the offending key from the known_hosts file on line 3, as the message said. You changed networking things, so IP addresses, etc., have changed, all of which figure into the SSH handshake. So, it's changed...and it's letting you know. Since you KNOW who made the change (you), remove the offending line, log in again, and it'll put an updated authorization line out there.
Remove the offending key from the known_hosts file on line 3, as the message said. You changed networking things, so IP addresses, etc., have changed, all of which figure into the SSH handshake. So, it's changed...and it's letting you know. Since you KNOW who made the change (you), remove the offending line, log in again, and it'll put an updated authorization line out there.
a
Thats exactly what I did, I k-lined the offending line, saved and logged in again to create a new known_hosts.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.