From owner-freebsd-current Fri Jun 12 08:36:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01009 for freebsd-current-outgoing; Fri, 12 Jun 1998 08:36:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ve7tcp.ampr.org (ve7tcp.ampr.org [198.161.92.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00999; Fri, 12 Jun 1998 08:36:08 -0700 (PDT) (envelope-from lyndon@ve7tcp.ampr.org) Received: from ve7tcp.ampr.org (localhost.ampr.org [127.0.0.1]) by ve7tcp.ampr.org (8.9.0/8.9.0) with ESMTP id JAA01665; Fri, 12 Jun 1998 09:35:22 -0600 (MDT) Message-Id: <199806121535.JAA01665@ve7tcp.ampr.org> To: The Hermit Hacker cc: 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." Date: Fri, 12 Jun 1998 09:35:21 -0600 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "The" == The Hermit Hacker writes: >> Use SASL instead. Unlike PAM, thee is an RFC for SASL. The> Boy, does that ever make alot of sense...both Solaris The> and Linux are adopting PAM as their authentication schemes, The> and are designing various modules for it, but let's adopt The> something because, hey, it has an RFC? IMAP4 and ACAP already use SASL. SMTP will shortly. You're going to have to install the infrastructure anyway, so you might as well use it. PAM is an adhoc bunch of gunk. I will take an RFC defined protocol any day over PAM, just because I want to know that my applications will be able to authenticate when I need them to. Anointment by Solaris or Linux does not an IETF standard make. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message