Date: Tue, 20 Jul 1999 08:28:25 -0600 From: Oscar Bonilla <obonilla@fisicc-ufm.edu> To: Joe Abley <jabley@patho.gen.nz> Cc: Oscar Bonilla <obonilla@fisicc-ufm.edu>, Wes Peters <wes@softweyr.com>, Mike Smith <mike@smith.net.au>, "David E. Cross" <crossd@cs.rpi.edu>, Dag-Erling Smorgrav <des@flood.ping.uio.no>, freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD Message-ID: <19990720082825.B793@fisicc-ufm.edu> In-Reply-To: <19990720225929.A9510@patho.gen.nz>; from Joe Abley on Tue, Jul 20, 1999 at 10:59:30PM %2B1200 References: <199907192111.OAA01326@dingo.cdrom.com> <3793ABE0.15090E38@softweyr.com> <19990719180026.A830@fisicc-ufm.edu> <19990720225929.A9510@patho.gen.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 20, 1999 at 10:59:30PM +1200, Joe Abley wrote: > On Mon, Jul 19, 1999 at 06:00:26PM -0600, Oscar Bonilla wrote: > > I agree. In solaris (and linux by the way) all you do is set > > passwd ldap files > > in /etc/nsswitch.conf > > and that's it. > > In Solaris, it's > > passwd: ldap files > ^ > > nsswitch.conf(4), SunOS 5.5.1: > > ... > There is an entry in /etc/nsswitch.conf for each database. > Typically these entries will be simple, such as "protocols: > files" or "networks: files nisplus". However, when multiple > sources are specified it is sometimes necessary to define > precisely the circumstances under which each source will be > tried. A source can return one of the following codes: > > Status Meaning > SUCCESS Requested database entry was found > UNAVAIL Source is not responding or corrupted > NOTFOUND Source responded "no such entry" > TRYAGAIN Source is busy, might respond to > retries > > For each status code, two actions are possible: > > Action Meaning > continue Try the next source in the list > return Return now > > The complete syntax of an entry is > > <entry> ::= <database> ":" [<source> [<criteria>]]* > <criteria> ::= "[" <criterion>+ "]" > <criterion> ::= <status> "=" <action> > <status> ::= "success" | "notfound" | "unavail" | "tryagain" > <action> ::= "return" | "continue" > ... > > Actually, this message is now bordering on the useful, when all I meant > to be was pedantic. I'll stop now, before I go too far; suffice to say > the Solaris implementation has some other elements worthy of consideration > if compatability is worth aiming for. > > It's maybe worth mentioning that /etc/host.conf might be a candidate for > the attic if the Solaris implementation was adopted on a wholesale basis > (i.e. including the "hosts:" key). > Couldn't we do this with /etc/auth.conf? What's the real purpose of this file? From the man page: "auth.conf contains various attributes important to the authentication code, most notably kerberos(5) for the time being." Isn't this what PAM is about? authentication? or does auth.conf cover the "other" part of authentication, basically the getpw* stuff? Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990720082825.B793>