From owner-freebsd-hackers Thu Oct 23 07:21:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA29090 for hackers-outgoing; Thu, 23 Oct 1997 07:21:14 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA29085 for ; Thu, 23 Oct 1997 07:21:04 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id XAA00411; Thu, 23 Oct 1997 23:47:11 +0930 (CST) Message-Id: <199710231417.XAA00411@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Colman Reilly cc: hackers@FreeBSD.ORG Subject: Re: Security Policies [Was: ACLs [Was: C2 Trusted FreeBSD?] ] In-reply-to: Your message of "Thu, 23 Oct 1997 14:09:08 +0100." <199710231309.OAA04169@monoid.cs.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Oct 1997 23:47:10 +0930 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [Deleted discussion about how difficult ACLs are to implement in UNIX] [Serious security model revamp proposal] > The main problem see (beyond the size of the task!) is where to store the > access control information. That too. Another would be making it clear to people how to work well with the new model(s). Having said all that, I'd still suggest that it's worth pursuing. If you approach the problem generalistically, you'd end up with something that could be applied to a not inconsiderable number of like systems, and achieve a pretty major breakthrough in that regard. mike