I had reformatted one of my hypervisor boxes (prox) and completely forgot about changing my SSH keys on other systems. I have a jumpbox that allows me to remotely access and admin the environment, but I couldn’t SSH into my prox system:<\/p>\n
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
\n@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
\n@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
\nIT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
\nSomeone could be eavesdropping on you right now (man-in-the-middle attack)!
\nIt is also possible that the RSA host key has just been changed.
\nThe fingerprint for the RSA key sent by the remote host is
\n2a:35:00:00:c7:e8:f3:fe:f7:6e:cf:00:00:db:e9:d8.
\nPlease contact your system administrator.
\nAdd correct host key in \/root\/.ssh\/known_hosts to get rid of this message.
\nOffending key in \/root\/.ssh\/known_hosts:33
\nRSA host key for prox1 has changed and you have requested strict checking.
\nHost key verification failed.\n<\/p><\/blockquote>\nOpening up my \/root\/.ssh\/known_hosts file I see a bunch of giberish. Answer found from c0rp<\/a>.<\/p>\n
Fast and easy fix<\/strong>
\nsed -i '33d' ~\/.ssh\/known_hosts<\/code>
\nObviously change the ’33d’ to reflect your line number. e.g line 12 wouild be ’12d’
\nThen SSH to your machine again and you’ll be asked if you want to store the new RSA fingerprint.<\/p>\nOr you can use SSH Keygen<\/strong>
\nssh-keygen -R yourmachinenamehere<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"I had reformatted one of my hypervisor boxes (prox) and completely forgot about changing my SSH keys on other systems. I have a jumpbox that allows me to remotely access and admin the environment, but I couldn’t SSH into my prox system: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE … Continue reading RSA host key for server has changed<\/span>