From owner-freebsd-hackers Wed Jul 21 9: 5:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id C935214DB1 for ; Wed, 21 Jul 1999 09:05:49 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id BAA17700; Thu, 22 Jul 1999 01:01:11 +0900 (JST) Message-ID: <3795EEB9.1A21EEA@newsguy.com> Date: Thu, 22 Jul 1999 01:00:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Oscar Bonilla Cc: Kris Kennaway , "David E. Cross" , Joe Abley , Wes Peters , Mike Smith , Dag-Erling Smorgrav , freebsd-hackers@FreeBSD.ORG Subject: Re: PAM & LDAP in FreeBSD References: <199907201520.LAA29350@cs.rpi.edu> <19990721094711.C1520@fisicc-ufm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oscar Bonilla wrote: > > There are three parts to the problem: > > 1. Where do we get the databases from? I mean, where do we get passwd, group, > hosts, ethers, etc from. > > This should be handled by a name service switch a la solaris. Basically > we want to be able to tell the system for each individual database where > to get the stuff from. We can add entries for each database in the system. I perceive here an unfair biasing toward nss. Someone mentioned defining where to get the passwords from based on the login class. This is a very interesting option, that doesn't seem to be well served by nss. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Your usefulness to my realm ended the day you made it off Hustaing alive." -- Sun Tzu Liao to his ex-finacee, Isis Marik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message