Date: Fri, 21 Nov 2003 23:26:31 -0600 From: Vulpes Velox <kitbsdlists@HotPOP.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: freebsd-questions@freebsd.org Subject: Re: login question Message-ID: <20031121232631.759e91e4.kitbsdlists@HotPOP.com> In-Reply-To: <443cchm6ip.fsf@be-well.ilk.org> References: <20031121210022.439cf0e0.kitbsdlists@HotPOP.com> <443cchm6ip.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Nov 2003 22:22:38 -0500 Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> wrote: > Vulpes Velox <kitbsdlists@HotPOP.com> writes: > > > Here is what I want to do... > > > > 1: Set up a server for storing users/groups/permissions/passwords. > > 2: Export it to other machines, with out exporting the file to all machines. > > 3: Set up other machines to check that when some on tries to login. > > > > How would I go about setting this up? > > > > I looked at Kerberos briefly in the handbook, but that only appeared to be > > for remote access. What or where should I look at for more information to > > set this up? > > 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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031121232631.759e91e4.kitbsdlists>