Date: Wed, 3 Sep 1997 22:35:30 +0300 (EEST) From: Narvi <narvi@haldjas.folklore.ee> To: John Fieber <jfieber@indiana.edu> Cc: hackers@FreeBSD.ORG Subject: Re: login.conf Message-ID: <Pine.BSF.3.96.970903223240.1315B-100000@haldjas.folklore.ee> In-Reply-To: <Pine.BSF.3.96.970903142345.9791C-100000@fallout.campusview.indiana.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Actually, it does not say so. Well, actually, it leaves the impression it does indeed control the authentification, the comment that it controls resource limits, accounting limits and default environment settings is too vague. There seems to be one word - "only" - missing from there. Sander There is no love, no good, no happiness and no future - all these are just illusions. On Wed, 3 Sep 1997, John Fieber wrote: > On Wed, 3 Sep 1997, Narvi wrote: > > > The end result is nothing, as it is still possible to login with the old > > unix passwd (provided it existed and is known). > > > > Why is that? Isn't login supposed to look at the auth style and judge by > > it which what kinds of passwds to accept? > > The authentication part of login.conf is currently unsupported, > at least in 2.2. If you have kerberos installed, it always tries > kerberos first, then the local password if kerberos fails. The > comments in login.conf hint that implementation is waiting on > external authentication modules, but I see no reason it *must* > wait. > > I have the opposite problem--I want to force use of local > passwords in some cases. > > -john > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970903223240.1315B-100000>