From owner-freebsd-security  Thu Nov 19 01:15:16 1998
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA05198
          for freebsd-security-outgoing; Thu, 19 Nov 1998 01:15:16 -0800 (PST)
          (envelope-from owner-freebsd-security@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA05193
          for <freebsd-security@FreeBSD.ORG>; Thu, 19 Nov 1998 01:15:15 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id BAA05412;
	Thu, 19 Nov 1998 01:13:51 -0800 (PST)
To: dima@best.net
cc: mark@grondar.za (Mark Murray), k.stevenson@louisville.edu,
        freebsd-security@FreeBSD.ORG
Subject: Re: PAM on FreeBSD (was Would this make FreeBSD more secure?) 
In-reply-to: Your message of "Wed, 18 Nov 1998 23:20:58 PST."
             <199811190720.XAA08602@burka.rdy.com> 
Date: Thu, 19 Nov 1998 01:13:51 -0800
Message-ID: <5409.911466831@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I wonder whether it's too late to change /usr/include/security to
> something else like /usr/include/pam

See the commit message.  John doesn't like it either, but there
are good reasons for it nonetheless.  Good enough for him to
exercise an option he himself found icky, anyway.

- Jordan

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