From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 19 Aug 2001 05:58:59 +0100 From: Dale Amon To: LeRoy Cressy Cc: SELinux@tycho.nsa.gov Subject: Re: [Fwd: Partial TOC for Comment] Message-ID: <20010819055859.D11122@vnl.com> References: <3B7C7C69.E7B84C68@earthlink.net> <20010817001226.J18183@vnl.com> <3B7D591A.EA28B00C@earthlink.net> <20010817122305.P18183@vnl.com> <3B7E54C4.E19EA07E@telocity.com> <20010818084601.A7060@vnl.com> <3B7FD0EE.398E6F02@telocity.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <3B7FD0EE.398E6F02@telocity.com> Sender: owner-selinux@tycho.nsa.gov List-Id: selinux@tycho.nsa.gov On Sun, Aug 19, 2001 at 10:45:02AM -0400, LeRoy Cressy wrote: > True, but doesn't selinux utilize all of the security measures built > into Unix/Linux from years gone by? Selinux is built on top of Linux > with improvements and not replacemants. > You must be missing the context of the discussion. We are discussing the design issues of the SELinux and the concepts of revocation via a security policy change at run time as discussed in the Flask papers on line, for use in Mr Scroggins book on SELinux. As I am no expert on SELinux, barely a neophyte even, I've suggested that one of the designers discuss this. We're not discussing general unix security methods, as that would be a bit off topic here. -- ------------------------------------------------------ Use Linux: A computer Dale Amon, CEO/MD is a terrible thing Village Networking Ltd to waste. Belfast, Northern Ireland ------------------------------------------------------ -- You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with the words "unsubscribe selinux" without quotes as the message.