Date: 22 Nov 2003 09:18:36 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Vulpes Velox <kitbsdlists@HotPOP.com> Cc: freebsd-questions@freebsd.org Subject: Re: login question Message-ID: <44vfpc8p1f.fsf@be-well.ilk.org> In-Reply-To: <20031121232631.759e91e4.kitbsdlists@HotPOP.com> References: <20031121210022.439cf0e0.kitbsdlists@HotPOP.com> <443cchm6ip.fsf@be-well.ilk.org> <20031121232631.759e91e4.kitbsdlists@HotPOP.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Vulpes Velox <kitbsdlists@HotPOP.com> writes: > On 21 Nov 2003 22:22:38 -0500 > Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > > This is exactly what Kerberos is good at. It's harder to administer > > than NIS, but doesn't require as much trust of the client machines. > > For yet another set of security profiles, LDAP can be useful. > > > > All of these (and, in fact, any scheme that remotely meets the rough > > criteria given) will require configuration on each client as well as > > the server. > > Yeah, know where I can actually find info on doing it thought? The handbook is a > little short on that... it has one small vague section... NIS and Kerberos5 both have their own sections in the Handbook. With pointers off to more (general) information. For LDAP, I don't offhand know of a good source of information on its pros and cons, but installing it is as simple as using the pam_ldap port and following the directions it prints out after install. To get more specific help, you'll need to be more specific in your questions, I'm afraid. Good luck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44vfpc8p1f.fsf>