On Fri, 23 Oct 2020, Jeremie Courreges-Anglas wrote: > > I upgraded my ports builder from snaps yesterday and I hit this when > running cvs up: > > --8<-- > russell ~$ ssh [email protected] > Warning: the ED25519 host key for 'ftp.hostserver.de' differs from the key > for the IP address '2a00:15a8:0:100:d91f:5023:0:1' > Offending key for IP in /home/jca/.ssh/known_hosts:2 > Matching host key in /home/jca/.ssh/known_hosts:12 > Are you sure you want to continue connecting (yes/no)? ^C > russell ~$ grep -n -F -e ftp.hostserver.de -e 217.31.80.35 -e > 2a00:15a8:0:100:d91f:5023:0:1 ~/.ssh/known_hosts > 1:ftp.hostserver.de,217.31.80.35 ecdsa-sha2-nistp256 > AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBF7jym1iJpFZfWWS+TTCGQv/CcVoFR4MVCR45YB6mmTL3V5bWwIQ8ggYGgbLcRV+M9VQL2zm0Nykw5HXbFXQ9D8= > 2:2a00:15a8:0:100:d91f:5023:0:1 ecdsa-sha2-nistp256 > AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBF7jym1iJpFZfWWS+TTCGQv/CcVoFR4MVCR45YB6mmTL3V5bWwIQ8ggYGgbLcRV+M9VQL2zm0Nykw5HXbFXQ9D8= > 11:ftp.hostserver.de,217.31.80.35 ssh-rsa > AAAAB3NzaC1yc2EAAAADAQABAAABAQDlCI96jPiGKnN07xj5ZhVPvo0gMo3TZOMtuf02afv9xm6+2vQlVqJThnavg3W0u6gaHV45MtldA/P4DaQbG50DPof9mJ3y1U2hbl+kU8tTfpVMC0WdXHbTpSmdkp5KVirFwZcubd2UFn8dXNtosULMahghvI2WzynLiO/hILzMrKE3J9LMG9mH2cbB3dAZ2KsHklQnrPb8xWhvaskcs3z94LgNyZbxF3uhOZBz019m5ba/DMjyoTLoNNNSRZ/Ur8JQIRSVzQPUwJ+AXCiZ8OoPF6RNmU9WjTFPt5K7dr4kOyZpDTBu103b2TUaJfiB/Gz2BNqyK11tLjLfXQO6Wez5 > 12:ftp.hostserver.de,217.31.80.35 ssh-ed25519 > AAAAC3NzaC1lZDI1NTE5AAAAIGtEuMXXJNl4whGkEOPWiq/XHgfzejdJvOKFL8S3kZDL > -->8-- > > I have "family inet6 inet4" on this machine, so IPv6 is tried first. > > On my laptop I hit the same issue with a dual-stack server of mine, both > with ssh -4 and ssh -6 <server> (I can provide details if needed). > > After cvs up -D2020/10/03, ./ssh/obj/ssh doesn't spit the warning, it > happens again with cvs up -D2020/10/04. > > cc'ing djm since this *looks* like fallout from the recent > UpdateHostKeys changes.
I think these were the problems that I fixed around 2020/10/14. If you remove line 12 from your known_hosts and reconnect with a ssh built after that then you should be fine. -d
