From owner-freebsd-isp  Wed Mar  5 07:44:13 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id HAA23186
          for isp-outgoing; Wed, 5 Mar 1997 07:44:13 -0800 (PST)
Received: from jennifer.pernet.net (jennifer.pernet.net [205.229.0.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA23174
          for <freebsd-isp@freebsd.org>; Wed, 5 Mar 1997 07:44:10 -0800 (PST)
Received: (from neal@localhost)
          by jennifer.pernet.net (8.8.4/8.8.4)
	  id JAA04888; Wed, 5 Mar 1997 09:44:15 -0600 (CST)
Date: Wed, 5 Mar 1997 09:44:15 -0600 (CST)
From: Neal Rigney <neal@pernet.net>
To: Michael Dillon <michael@memra.com>
cc: freebsd-isp@freebsd.org
Subject: Re: radius aware pop3 server
In-Reply-To: <Pine.BSI.3.93.970305062752.12357B-100000@sidhe.memra.com>
Message-ID: <Pine.BSF.3.91.970305094042.4768B-100000@jennifer.pernet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 5 Mar 1997, Michael Dillon wrote:

[snip]
> IMHO, RADIUS authentication should be available as a config option
> everywhere passwd lookups are used such as in the login command, ftp
> server, etc.
[snip]

I've thought about doing this also(patching in RADIUS), but how would you 
handle simple getpw*() calls?  The Radius specs(as I read them) *require* 
a password to be transmitted in auth packets.  The only thing I could 
think of is to hack the server to accept a "generic" password to return 
passwd info.  Any thoughts?  Am I just crazy?

--
Neal Rigney, PERnet Communications, (409)729-4638
neal@mail.pernet.net