On Thu, 29 Oct 2020, Jeremie Courreges-Anglas wrote: > On Thu, Oct 29 2020, Damien Miller <[email protected]> wrote: > > On Wed, 28 Oct 2020, Jeremie Courreges-Anglas wrote: > > > >> On Wed, Oct 28 2020, Damien Miller <[email protected]> wrote: > >> > On Mon, 26 Oct 2020, Jeremie Courreges-Anglas wrote: > >> > > >> >> On Fri, Oct 23 2020, Damien Miller <[email protected]> wrote: > >> >> > 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: > >> > > >> > [big snip] > >> > > >> > I think I have replicated your problem. Can you roll your known_hosts > >> > back to just the ecdsa-sha2-nistp256 keys, apply this patch and attempt > >> > a few connections? You should see no more conflicts between IPv4/IPv6 > >> > addresses. > >> > >> Here's a v6->v4 case which didn't improve. I believe that the data > >> provided below should help you reproduce the issue, if not there's > >> something weird going on. Feel free to send more patches my way. > > > > Thanks - I think the following patch should fix it. If it doesn't > > then can you please rerun your testing with some extra logging: > > > > ssh -oLogVerbose=sshconnect.c:*,clientloop.c:*,hostfile.c:* ... > > No new host keys and no warnings this time:
Thanks for catching this and your help in wrestling it to the ground :) I'll commit it shortly. -d
