From owner-freebsd-current Thu Jun 11 23:43:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14370 for freebsd-current-outgoing; Thu, 11 Jun 1998 23:43:03 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles357.castles.com [208.214.167.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14350; Thu, 11 Jun 1998 23:42:57 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id WAA00405; Thu, 11 Jun 1998 22:38:11 -0700 (PDT) Message-Id: <199806120538.WAA00405@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: The Hermit Hacker cc: Terry Lambert , isp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Radius login via getty In-reply-to: Your message of "Thu, 11 Jun 1998 22:30:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Jun 1998 22:38:11 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 12 Jun 1998, Terry Lambert wrote: > > > Actually, I believe that solaris is moving towards using PAM for > > > all this too...each of the above, I believe, already has a pam module out > > > there for it... > > > > 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? This is the "20 million flies" argument. PAM is broken as designed; implementing it might be expedient, but will never be "right". -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message