Quoting Andrew Morgan ([EMAIL PROTECTED]):
-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:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
0. fix the implementation of cap_setpcap. It is supposed to mean 'this
process can raise capabilities, outside its permitted set, in _its own_
inheritable set'.
A few clarification questions:
Process p1 is calling
--- Joshua Brindle [EMAIL PROTECTED] wrote:
Casey Schaufler wrote:
--- 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
Quoting Andrew Morgan ([EMAIL PROTECTED]):
My current working preference is: 0, 3, 1, 2. I don't consider any of
them as urgent as getting the inode modification protection fixed.
Oops. Right.
I'm not sure I'll have a laptop with me tomorow, but I'll try to get a
patch out no later than
