From owner-freebsd-current Sun Feb 2 20:37:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA07443 for current-outgoing; Sun, 2 Feb 1997 20:37:13 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA07438 for ; Sun, 2 Feb 1997 20:37:10 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id EAA06503; Mon, 3 Feb 1997 04:35:41 GMT Date: Mon, 3 Feb 1997 13:35:41 +0900 (JST) From: Michael Hancock To: Michael Smith cc: David Nugent , terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Subject: login.conf - radius client (was Re: getty patches) In-Reply-To: <199702030348.OAA02656@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 3 Feb 1997, Michael Smith wrote: > David Nugent stands accused of saying: > > > > > I'm not aware that the current login.conf code is capable of running > > > the commercial authenticators... I'd be happy to be corrected. > > > > You're quite correct. The reason that authentication is not > > available is lack of information, pure and simple. I'm still > > waiting for information from either/both sef and BSDI on it, > > and how the API is intended to work. There are quite a few > > ambiguities to resolve. Currently login(1) includes the > > relevant code to support them, but it is not compiled in. > > I am _particularly_ interested in this, as I have a couple of (paying) > ISP customers who very much want to integrate user logins to BSD > machines with their radius authentication environment. > This would be very interesting indeed. Centralized authentication to a radiusd box for everything; an ASCEND box, a FreeBSD PPP server, a FreeBSD client PC, etc. Regards, Mike Hancock