Re: Desktop Kernel Stuff



> That's kind of interesting - it seems to address file change
> notification as well, doesn't it? i.e. you could have an "access
> control agent" that just always allowed access, but recorded each 
> access and sent out notification.

This is in fact mandatory for certain security standards

> Seems like there might be some performance concerns with involving a
> userspace daemon thingy in every open/close, though?

There would but if you just what notifications not yes/no rulings you can
buffer them in kernel space.



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