Research
Skip Research Menus
Research MenuSecurity Enhanced Linux What's New Frequently Asked Questions Background Documents License Download Participating Mail List Archives Remaining Work Contributors Related Work Press Releases Information Assurance Research NIARL In-house Research Areas Mathematical Sciences Program Sabbaticals Computer & Information Sciences Research Technology Transfer Advanced Computing Advanced Mathematics Communications & Networking Information Processing Microelectronics Other Technologies Technology Fact Sheets Publications Related Links |
SELinux Mailing ListRe: [RFC] [PATCH]
From: Darrel Goeddel <dgoeddel_at_TrustedCS.com>
Date: Fri, 17 Feb 2006 10:23:38 -0600
>>It would seem to me that we need the current functionality of keeping all rules >>that are set up and revalidating them upon policy loads. If we don't do it here, >>it would need to be done at the audit layer - it might not be as pretty there. > > > > I don't know... My first thoughts are that it seems like the audit > layer should be ignorant of policy loads/reloads--that's not really it's > business. I was trying to avoid knowledge of policy reloads (and really policy in general) with the rule skipping piece and the sequo checking when the rule is used. As far as the audit system is concerned, SELinux could be rolling dice to determine matches. As for the big picture. Steve Grubb suggested a compromise of keeping the current methodology and enhancing it with KERN_INFO messages. I'd suggest message for the following:
Does that fit the bill? -- Darrel -- This message was distributed to subscribers of the selinux mailing 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.Received on Fri 17 Feb 2006 - 11:24:03 EST |
|
Date Posted: Jan 15, 2009 | Last Modified: Jan 15, 2009 | Last Reviewed: Jan 15, 2009 |