Follow-up Comment #12, sr #110545 (project administration):
[comment #10 comment #10:]
> The problem is triggered by the deprecation of SHA1 hashes in the new
OpenSSH 8.8 release from last week. Which prevents the host key from being
accepted. I am not sure why switching to an ed25519 key avoids this. But if
that works then great as ed25519 keys are both stronger and more compact.
They will likely become the default in a future release.
Just in case this help other, this issue manifests for me as a "Host key
verification failed":
$ git pull
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ 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 ED25519 key sent by the remote host is
SHA256:o/oI4CKKcWc4cZvDFEdmOXsE3tiPP8bWa04h4bQjtV4.
Please contact your system administrator.
Add correct host key in /home/ben/.ssh/known_hosts to get rid of this
message.
Offending RSA key in /home/ben/.ssh/known_hosts:199
Host key for git.sv.gnu.org has changed and you have requested strict
checking.
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The `HostkeyAlgorithms` and `PubkeyAcceptedAlgorithms` overrides below work
for me.
Regards,
Ben
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?110545>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
