Date: Fri, 10 Sep 2021 13:02:57 +0200 From: Gary Jennejohn <gljennjohn@gmail.com> To: Ed Maste <emaste@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: OpenSSH issue: 14-Current rejects non-publickey scp/ssh/rsync connectiosn all of the sudden Message-ID: <20210910110257.5556af40@ernst.home> In-Reply-To: <20210910082946.3f31c6e7@ernst.home> References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> <CAPyFy2Cq-X60iiMGx%2BqFZwxad95PMOpVfftVqMw-iurGnAZiVg@mail.gmail.com> <20210910082946.3f31c6e7@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 Sep 2021 10:29:46 +0200 Gary Jennejohn <gljennjohn@gmail.com> wrote: > On Thu, 9 Sep 2021 19:37:39 -0400 > Ed Maste <emaste@freebsd.org> wrote: > > > On Thu, 9 Sept 2021 at 15:18, FreeBSD User <freebsd@walstatt-de.de> wrote: > > > > > > /etc/ssh/sshd_config line 89: Unsupported option UsePAM > > > > Sorry, it turns out I had the wrong version of config.h in my commit. > > > > I'm running a build now and will commit it once a test with that > > change passes. I will look into all of the reported issues, but I'd be > > much obliged if you can rebuild sshd and try again (once the config.h > > commit lands). > > > > This is interesting. > > Was the config.h in the patch the same as the one you committed? > > When I ran my tests one machine was running the new ssh (from the > patch) and the other was running the old ssh, and I didn't have any > connection errors. > I now have two HEAD systems running the latest world and ssh works again. Yay! -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210910110257.5556af40>