From owner-freebsd-questions@FreeBSD.ORG Fri Nov 21 21:28:05 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA96916A4CE for ; Fri, 21 Nov 2003 21:28:05 -0800 (PST) Received: from lakemtao06.cox.net (lakemtao06.cox.net [68.1.17.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BE0E43FDF for ; Fri, 21 Nov 2003 21:28:04 -0800 (PST) (envelope-from kitbsdlists@HotPOP.com) Received: from fortytwo ([68.109.49.234]) by lakemtao06.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with SMTP id <20031122052802.CHJQ24575.lakemtao06.cox.net@fortytwo>; Sat, 22 Nov 2003 00:28:02 -0500 Date: Fri, 21 Nov 2003 23:26:31 -0600 From: Vulpes Velox To: Lowell Gilbert 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> X-Mailer: Sylpheed version 0.9.6claws (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: login question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2003 05:28:06 -0000 On 21 Nov 2003 22:22:38 -0500 Lowell Gilbert wrote: > Vulpes Velox 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...