From owner-freebsd-isp  Wed Jul  5  7: 1:54 2000
Delivered-To: freebsd-isp@freebsd.org
Received: from durango.picus.com (durango.picus.com [209.100.20.19])
	by hub.freebsd.org (Postfix) with ESMTP id 5E2C837B8CD
	for <freebsd-isp@freebsd.org>; Wed,  5 Jul 2000 07:01:50 -0700 (PDT)
	(envelope-from troy@picus.com)
Received: from arcadia [209.100.20.198] by durango.picus.com
  (SMTPD32-5.05) id AF43CB40218; Wed, 05 Jul 2000 09:59:31 -0400
Reply-To: <troy@picus.com>
From: "Troy Settle" <troy@picus.com>
To: "Andy Cowan" <andyc@waverider.net.uk>
Cc: <freebsd-isp@freebsd.org>
Subject: RE: Centralised user information
Date: Wed, 5 Jul 2000 10:00:57 -0400
Message-ID: <NIEBLEDADLBOBAJFKPHDAEIOCAAA.troy@picus.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <NDBBKECBEEIIPEFNBPBFCEPKCIAA.andyc@waverider.net.uk>
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Andy,

At my last job, we used custom script to distribute an edited password file
to other machines when needed (at 5 minute intervals).  Not a perfect
solution, but it worked well enough.

Another option, is to use NIS.  See /var/yp/Makefile.dist for details.

--
  Troy Settle
  Network Analyst
  Picus Communications
  540.633.6327

It's always a long day... 86400 doesn't fit into a short


** -----Original Message-----
** From: owner-freebsd-isp@FreeBSD.ORG
** [mailto:owner-freebsd-isp@FreeBSD.ORG]On Behalf Of Andy Cowan
** Sent: Wednesday, July 05, 2000 9:44 AM
** To: Bob Martin
** Cc: freebsd-isp@freebsd.org
** Subject: RE: Centralised user information
**
**
** > > What are people out there using for holding centralised login
** > information?
** > > The objective is to allow a cluster of servers to
** authenticate against a
** > > centralised database (using Radius, LDAP, or any other
** > mechanism really).
** > >
** > Radiator. We use it for everything from account logins to routers.
** >
**
** But how do you tie radiator (or any other radius for that
** matter) to the OS,
** so that when sendmail attempts to deliver, or qpopper tries to
** authenticate,
** or apache looks up a users homedir - you get the picture....
**
** How can you make the OS itself retrieve user info from Radius?
**
** A.
**
** --
** Andy Cowan
** Managing Director
** Wave Rider Internet Ltd
** http://www.waverider.co.uk
**
**
**
** To Unsubscribe: send mail to majordomo@FreeBSD.org
** with "unsubscribe freebsd-isp" in the body of the message
**



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message