Date: Fri, 17 Sep 2021 15:30:19 +0200 From: FreeBSD User <freebsd@walstatt-de.de> To: Ed Maste <emaste@freebsd.org> Cc: gljennjohn@gmail.com, 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: <20210917153046.3be83f09@thor.intern.walstatt.dynvpn.de> In-Reply-To: <CAPyFy2CK7JiuUupYiuaTYKgVoG2CrV4oPDKvEVXt0=2C_XLuFg@mail.gmail.com> References: <20210909211530.5cf712d7@thor.intern.walstatt.dynvpn.de> <CAPyFy2Cq-X60iiMGx%2BqFZwxad95PMOpVfftVqMw-iurGnAZiVg@mail.gmail.com> <20210910082946.3f31c6e7@ernst.home> <CAPyFy2CK7JiuUupYiuaTYKgVoG2CrV4oPDKvEVXt0=2C_XLuFg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Fri, 10 Sep 2021 09:04:30 -0400 Ed Maste <emaste@freebsd.org> schrieb: > On Fri, 10 Sept 2021 at 04:29, Gary Jennejohn <gljennjohn@gmail.com> wrote: > > > > Was the config.h in the patch the same as the one you committed? > > No it wasn't - USE_PAM was #defined in config.h after applying the > patch, while the committed version accidentally did not. > Hello out there, Just for clarification: after the last patches to the tree regarding openssh and recompilation of the base system, it seemed that everything turned to normal afterwards - in my case. Thanks. Kind regards, O. Hartmann -- O. Hartmann
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210917153046.3be83f09>