From owner-freebsd-current@FreeBSD.ORG Mon Apr 12 22:06:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF4A216A4CE for ; Mon, 12 Apr 2004 22:06:07 -0700 (PDT) Received: from miffy.openlook.org (openlook.org [211.236.182.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DC4743D4C for ; Mon, 12 Apr 2004 22:06:07 -0700 (PDT) (envelope-from perky@miffy.openlook.org) Received: by miffy.openlook.org (Postfix, from userid 1000) id 01CBFA969; Tue, 13 Apr 2004 14:06:05 +0900 (KST) Date: Tue, 13 Apr 2004 14:06:05 +0900 From: Hye-Shik Chang To: Julian Elischer Message-ID: <20040413050605.GA1482@i18n.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Accept-Language: ko, en User-Agent: Mutt/1.5.5.1i X-Mailman-Approved-At: Tue, 13 Apr 2004 04:50:20 -0700 cc: FreeBSD current users Subject: Re: libradius patches (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 05:06:07 -0000 On Mon, Apr 12, 2004 at 06:51:30PM -0700, Julian Elischer wrote: > > Is there someone here who knows radius who can test these > additions to libradius? > > julian > > ---------- Forwarded message ---------- > Date: Mon, 12 Apr 2004 17:31:23 -0500 (CDT) > From: Archie Cobbs > To: julian@elischer.org > Subject: libradius (fwd) > > Hey Julian, > > I want to check in these changes (after a few grammatical fixes) > to -current, however, I'm not very "current".. i.e., I don't even > subscribe to freebsd-current anymore and if the build breaks or > something then I'll probably not find out about it until everybody > is mad at me. Plus I don't have a 5.x machine to test on, though > Michael has already tested them. > > [...] > I verified that this code generates correct Message-Authenticator and checks response packets correctly. And it won't break any non-EAP authentications currently supported. But didn't look into MPPE implementations yet. Hye-Shik