Date: Mon, 3 Feb 1997 13:35:41 +0900 (JST) From: Michael Hancock <michaelh@cet.co.jp> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: David Nugent <davidn@unique.usn.blaze.net.au>, terry@lambert.org, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Subject: login.conf - radius client (was Re: getty patches) Message-ID: <Pine.SV4.3.95.970203132957.6439A-100000@parkplace.cet.co.jp> In-Reply-To: <199702030348.OAA02656@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.95.970203132957.6439A-100000>