From owner-freebsd-security Fri Nov 26 7:44:42 1999 Delivered-To: freebsd-security@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id BBE1014BE6 for ; Fri, 26 Nov 1999 07:44:33 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA60836; Fri, 26 Nov 1999 10:44:22 -0500 (EST) (envelope-from wollman) Date: Fri, 26 Nov 1999 10:44:22 -0500 (EST) From: Garrett Wollman Message-Id: <199911261544.KAA60836@khavrinen.lcs.mit.edu> To: Robert Watson Cc: David Wolfskill , security@FreeBSD.ORG Subject: Re: ps on 4.0-current In-Reply-To: References: <199911241622.IAA25297@pau-amma.whistle.com> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > The painful thing is getting ACLs into the underlying storage mechanism, > not writing kernel ACL support -- I've finished the framework in the > kernel, libraries, some userland utilities, and even default evaluation > routines for file systems to call. I just don't want to screw around with > FFS storage and soft updates :-). I think it would be a Great Thing if this were incorporated into -current before the feature freeze (which is coming up RSN). Even if it's not implemented in any file systems yet, it would be good to get the API fixed and out in public so that people can write their software to it. It might also be the motivating factor to actually getting a filesystem hacker to work on that side of things. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message