From owner-freebsd-isp  Fri Jun 27 00:46:54 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA09661
          for isp-outgoing; Fri, 27 Jun 1997 00:46:54 -0700 (PDT)
Received: from radford.i-plus.net (root@Radford.i-Plus.net [206.99.237.6])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA09656
          for <freebsd-isp@FreeBSD.ORG>; Fri, 27 Jun 1997 00:46:51 -0700 (PDT)
Received: from abyss.i-Plus.net (pitlord@Abyss.i-Plus.net [206.99.237.44])
	by radford.i-plus.net (8.8.5/8.8.5) with SMTP id DAA27185;
	Fri, 27 Jun 1997 03:45:19 -0400 (EDT)
Message-Id: <199706270745.DAA27185@radford.i-plus.net>
X-Mailer: Microsoft Outlook Express 4.71.0544.0
From: "Troy Settle" <rewt@i-Plus.net>
To: <tomthai@future.net>, "Chris Shenton" <chris@absinthe.i3inc.com>
Cc: <freebsd-isp@FreeBSD.ORG>, <linuxisp@friendly.jeffnet.org>
Subject: Re: system passwd to RADIUS
Date: Sat, 28 Jun 1997 03:49:04 -0400
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-MimeOLE: Produced By Microsoft MimeOLE Engine V4.71.0544.0
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

From: Chris Shenton <chris@absinthe.i3inc.com>
>BTW: I hacked Ascend's RADIUS to treat the password entry listed in
>RADIUS users file as a crypted passwd. I think all I had to to was run
>what the RADIUS client sent to the server through crypt() then let it
>compare with what RADIUS parsed from the user file. You could get
>clever and evan modify it to use forms like
>
> Password = crypt."cx19azPss3v97"
>
>in addition to normal clear-text ones. I don't like cleartext
>passwords, so I didn't bother. The code was for Ascend's RADIUS so
>posting it here probably wouldn't help. Just look where it does the
>compare with what the client (comm server) sent with what's in the
>users file.

I don't like cleartext passwords either, but have been forced to use them
by the PPP protocol :(
seems that MPP won't work without CHAP, and CHAP won't work with encrypted
passwords.

Anyone know a way around this?

Thanks,

Troy Settle <st@i-Plus.net>
Network Administrator, iPlus Internet Services
http://www.i-Plus.net 

PS: is the linuxisp list back up?  or is that just wishful thinking?