From owner-freebsd-current  Wed Mar  4 23:16:18 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA19386
          for freebsd-current-outgoing; Wed, 4 Mar 1998 23:16:18 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA19381
          for <freebsd-current@freebsd.org>; Wed, 4 Mar 1998 23:16:17 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 0yAUst-0000Mg-00; Wed, 4 Mar 1998 23:16:03 -0800
Date: Wed, 4 Mar 1998 23:15:59 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Andrzej Bialecki <abial@nask.pl>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: PAM and friends
In-Reply-To: <Pine.NEB.3.95.980305074206.14375A-100000@korin.warman.org.pl>
Message-ID: <Pine.BSF.3.96.980304231105.23157B-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Thu, 5 Mar 1998, Andrzej Bialecki wrote:

> Hi!
> 
> Is there any work behind the scenes on PAM-ification? I am about to edit

  PAM seems to be a bit of dead duck these days.  Too inflexible, and not
secure unless used on the console.

  I'm looking at SASL.  Seems to be a new and better generic auth
solution.

Tom




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message