Never gotten that error with GitHub before, but gotten it many times for
ordinary SSH connections where the host key has changed.
The error message usually tells which line in your .ssh/known_hosts file
has the previous fingerprint.
Once the new key has been vetted, you can simply delete that line from
your .ssh/known_hosts file, then accept the new fingerprint.
-- R; <><
On 3/24/23 08:43, Lionel B. Dyck wrote:
GitHub changed their RSA SSH Host Key and now there are issues. Here is
their announcement:
https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/
This is what you may see:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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:uNiVztksCsDhcc0u9e8BujQXVUpKZIDTMczCvj3tD2s.
Please contact your system administrator.
Add correct host key in ~/.ssh/known_hosts to get rid of this message.
Host key for github.com has changed and you have requested strict checking.
Host key verification failed.
Lionel B. Dyck <><
Website: https://www.lbdsoftware.com
Github: https://github.com/lbdyck
“Worry more about your character than your reputation. Character is what you
are, reputation merely what others think you are.” - - - John Wooden
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
