From owner-freebsd-current Thu Jun 11 19:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07683 for freebsd-current-outgoing; Thu, 11 Jun 1998 19:31:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07637; Thu, 11 Jun 1998 19:30:52 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id WAA01519; Thu, 11 Jun 1998 22:30:45 -0400 (EDT) Date: Thu, 11 Jun 1998 22:30:45 -0400 (EDT) From: The Hermit Hacker To: Terry Lambert cc: isp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Radius login via getty In-Reply-To: <199806120136.SAA07321@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 12 Jun 1998, Terry Lambert wrote: > > > Really, what we're looking at here, is something like Solaris' > > > /etc/nsswitch.conf. However, that does bring a whole baggage of > > > > 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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message