think you are.” - - - John Wooden
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Rick Troth
Sent: Friday, March 24, 2023 9:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GitHub Update - Arg!
It's all about trust.
SO glad you posted, and esp that you found the ann
--Original Message-
From: IBM Mainframe Discussion List On Behalf Of
René Jansen
Sent: Friday, March 24, 2023 8:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GitHub Update - Arg!
Thanks Lionel, that was just in time!
best regards,
René.
On 24 Mar 2023, at 13:43, Lionel B. Dyck wrot
- - John Wooden
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
René Jansen
Sent: Friday, March 24, 2023 8:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: GitHub Update - Arg!
Thanks Lionel, that was just in time!
best regards,
René.
> On 24 Mar 2023, at 13:43, Li
Thanks Lionel, that was just in time!
best regards,
René.
> On 24 Mar 2023, at 13: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
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
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! @
