[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]


Dustin Kirkland wrote:
On Fri, 2006-02-17 at 08:43 -0600, Darrel Goeddel wrote:

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

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

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

- a rule that is inactive is inserted
- a rule that was active becomes inactive
- a rule that was inactive becomes active

Does that fit the bill?



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]