Date: Mon, 12 Feb 2001 00:43:43 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: John Reynolds <jjreynold@home.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: sshd in 4.2-STABLE Message-ID: <200102120843.f1C8hhM03375@earth.backplane.com> References: <1843641235.20010212104321@road.omskelecom.ru> <Pine.BSF.4.31.0102112212490.55276-100000@mx.dmz.orem.verio.net> <14983.29328.298241.606895@whale.home-net>
next in thread | previous in thread | raw e-mail | index | archive | help
:[ On Sunday, February 11, Aaron Mildenstein wrote: ]
:> I had the same problem. And do you know what I found was the problem?
:> /etc/pam.conf
:> was missing the following lines:
:>
:> sshd auth sufficient pam_skey.so
:> sshd auth required pam_unix.so try_first_pass
:> sshd session required pam_permit.so
:>
:> And that was all it took to get sshd to work right.
:> Somewhere in there sshd started requiring pam. Go figure.
:
:Yes, but always always always running "mergemaster" (or if you are sadistic,
:doing it by hand) to update /etc/ will avoid gotchas like this. Everybody
:tracking -STABLE should also be looking at the RELENG_4 relevent bits from
:cvs-all too, just so that you spot a change and your brain and register it.
:
:-Jr
:
:--
:=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
:John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation
... or maybe installworld should just check to see if /etc/pam.conf is
the unmodified older version and overwrite it with /usr/src/etc/pam.conf
by default, rather then create little gotchas for people trying to
upgrade. Hmmmmmm.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102120843.f1C8hhM03375>