From owner-freebsd-amd64@FreeBSD.ORG  Sun Jun 13 02:31:00 2010
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8B470106566C
	for <freebsd-amd64@FreeBSD.org>; Sun, 13 Jun 2010 02:31:00 +0000 (UTC)
	(envelope-from famd64@paz.bz)
Received: from mail.qcislands.net (mail.qcislands.net [207.34.147.83])
	by mx1.freebsd.org (Postfix) with ESMTP id 7184A8FC19
	for <freebsd-amd64@FreeBSD.org>; Sun, 13 Jun 2010 02:31:00 +0000 (UTC)
Received: from [209.53.164.100] (helo=[192.168.1.4])
	by mail.qcislands.net with esmtp (Exim 4.71)
	(envelope-from <famd64@paz.bz>) id 1ONcyP-000OhY-Tl
	for freebsd-amd64@FreeBSD.org; Sat, 12 Jun 2010 19:30:59 -0700
Message-ID: <4C1442E2.9070300@paz.bz>
Date: Sat, 12 Jun 2010 19:30:58 -0700
From: Jim Pazarena <famd64@paz.bz>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: freebsd-amd64@FreeBSD.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-local_scan: locally submitted (100)
Cc: 
Subject: radiusd-cistron on FreeBSD 8.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jun 2010 02:31:00 -0000

I recently attempted to move my radius authentication from a 7.0 i386
radiusd-cistron 1.6.8 to an 8.0 amd64.

radius consistently failed the user authentication all-the-while
logging some crazy garbage in the failed password field of the log.

I suspected that the encryption key was incorrect in the clients file,
so I verified that it was correct in accordance with the RAS.

I also 'changed' the encryption key on both clients file and the RAS
and still the log showed garbage in the log.

I swung back to the 7.0 i386 machine (with the NEW key), and authentication
was instant and positive.

I don't know if the issue was amd64 vs i386, or 7.0 vs 8.0 or BOTH.
Any suggestions would be appreciated. Anxious to start using my new
8.0 amd64 box.

Jim