From owner-freebsd-questions@FreeBSD.ORG Mon Sep 8 20:28:19 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 1B01F16A4BF for ; Mon, 8 Sep 2003 20:28:18 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BCA343FEA for ; Mon, 8 Sep 2003 20:28:18 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h893SHVp089311; Mon, 8 Sep 2003 22:28:17 -0500 (CDT) (envelope-from dan) Date: Mon, 8 Sep 2003 22:28:17 -0500 From: Dan Nelson To: Tillman Hodgson Message-ID: <20030909032816.GN48339@dan.emsphone.com> References: <200309082359.07548.ajacoutot@lphp.org> <20030908161045.C11841@seekingfire.com> <42065386.1063047726@[192.168.10.11]> <20030908181529.P11841@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030908181529.P11841@seekingfire.com> X-OS: FreeBSD 5.1-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: freebsd-questions@freebsd.org Subject: Re: nis security 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: Tue, 09 Sep 2003 03:28:19 -0000 In the last episode (Sep 08), Tillman Hodgson said: > > > I'm a bit biased, however: I use NIS with Kerberos and think it's the > > > cats pajamas :-) > > > > This sounds exactly like what we are looking for. Can you point us > > to any docs explaining how you do this?? > > The rough instructions are fairly simple: > > * Set up Kerberos and ensure you have a working realm > * Set up NIS, but set all the passwd fields to something that doesn't > map to a real password (I like 'krb5', others like '*') You can do something similar with LDAP, by using pam_ldap for authentication and NIS for the rest of the user info lookup. -- Dan Nelson dnelson@allantgroup.com