From owner-freebsd-hackers Tue Apr 22 18:36:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA23757 for hackers-outgoing; Tue, 22 Apr 1997 18:36:04 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA23707; Tue, 22 Apr 1997 18:35:58 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.4) with SMTP id VAA26621; Tue, 22 Apr 1997 21:35:40 -0400 (EDT) Date: Tue, 22 Apr 1997 21:35:40 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: Michael Smith cc: freebsd-isp@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: Need a common passwd file among machines In-Reply-To: <199704210703.QAA08288@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Apr 1997, Michael Smith wrote: > "So what" is that the new Livingston code is Radius-2 compliant, and has > lots of nice features. What is "Radius-2 compliant"? AFAIK the only compliance that matters is RFC2138. The code at ftp://ftp.merit.edu/radius/releases/radius.23c.basic.tar.gz is free and is nearly compliant. (Actually the Livingston code is not compliant with the RFC either because they used port 1645 when it was already assigned.) The new features of the Livingston code are basically superficial junk like user menus and prefix/suffix support. pbd -- Why can't you be a non-conformist like everyone else?