From owner-freebsd-current Thu Jun 11 20:33:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18372 for freebsd-current-outgoing; Thu, 11 Jun 1998 20:33:46 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18365 for ; Thu, 11 Jun 1998 20:33:42 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id UAA07505; Thu, 11 Jun 1998 20:33:26 -0700 (PDT) (envelope-from jdp) Message-Id: <199806120333.UAA07505@austin.polstra.com> To: scrappy@hub.org Subject: Re: Radius login via getty In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 11 Jun 1998 20:33:26 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , The Hermit Hacker wrote: > On Fri, 12 Jun 1998, Terry Lambert wrote: > > > PAM has a number of known problems. > > > > Use SASL instead. Unlike PAM, thee is an RFC for SASL. > > Boy, does that ever make alot of sense...both Solaris and Linux > are adopting PAM as their authentication schemes, and are designing > various modules for it, but let's adopt something because, hey, it has an > RFC? Yes, and if you read the SASL RFC (RFC 2222) you'll find that it says practically nothing concrete. Let's just say it didn't raise my pulse rate any when I read it. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message