Quoting Andrew Morgan ([EMAIL PROTECTED]):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Yes. I'd thought about adding a security_ops-inode_change() or
somesuch hook, but there were two reasons I didn't. First, this
should be done whether or not the capability
--- Andrew Morgan [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Meanwhile, any chance you would get some time to implement the cap_bset
vs fcaps change you wanted? I'd have to look at my checklist to be
sure, but I think that, a version
Casey Schaufler wrote:
--- Joshua Brindle [EMAIL PROTECTED] wrote:
... On the guard
implementation I'd like to note that assured pipelines are pretty hard
to get right. Without object class and create granularity (at the very
least) you might find it very difficult to control backflow.
--- Joshua Brindle [EMAIL PROTECTED] wrote:
Casey Schaufler wrote:
--- Joshua Brindle [EMAIL PROTECTED] wrote:
... On the guard
implementation I'd like to note that assured pipelines are pretty hard
to get right. Without object class and create granularity (at the very
diff -uprN -X linux-2.6.22-base/Documentation/dontdiff
linux-2.6.22-base/security/smack/smack_lsm.c
linux-2.6.22/security/smack/smack_lsm.c
--- linux-2.6.22-base/security/smack/smack_lsm.c1969-12-31
16:00:00.0
-0800
+++ linux-2.6.22/security/smack/smack_lsm.c 2007-07-24
