From: Martin Sebor <msebor@gmail.com>
To: overseers@sourceware.org
Subject: ssh key conflicts
Date: Fri, 22 May 2020 08:46:57 -0600 [thread overview]
Message-ID: <ed53ccca-d52b-57f9-239a-97c7d0b875a0@gmail.com> (raw)
Lately, every time after I do git pull from glibc and I git pull
gcc I get this:
Warning: the RSA host key for
'gcc.gnu.org' differs from the key for the IP address '8.43.85.97'
Offending key for IP in /home/msebor/.ssh/known_hosts:18
Matching host key in /home/msebor/.ssh/known_hosts:1
Are you sure you want to continue connecting (yes/no)?
So I go and delete the offending key, but the next time I pull
the warning is back, and unless I delete the offending key I get:
Connection closed by 8.43.85.97 port 22
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
After I do delete it I can pull gcc fine but when I try to pull
glibc I get this:
The authenticity of host 'sourceware.org (8.43.85.97)' can't be established.
ECDSA key fingerprint is SHA256:4bqfulMjMg7/L/38MJBw7mVMMu6EH+3MgMitrCRdFho.
This didn't use to happen. I read various suggestions online (in
addition to deleting the offending key as I've been doing also to
add CheckHostIP no in my ~/.ssh/config) but before I use them let
me ask: am I doing something wrong and/or what is the recommended
cure for this in our case?
Thanks
Martin
next reply other threads:[~2020-05-22 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 14:46 Martin Sebor [this message]
2020-05-22 15:09 ` Frank Ch. Eigler
2020-05-22 15:31 ` Martin Sebor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed53ccca-d52b-57f9-239a-97c7d0b875a0@gmail.com \
--to=msebor@gmail.com \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).