Messages in this thread | | | Date | Fri, 24 Apr 2015 16:15:11 -0500 | From | "Serge E. Hallyn" <> | Subject | Re: [RFC] capabilities: Ambient capabilities |
| |
On Fri, Apr 24, 2015 at 01:18:44PM -0700, Andy Lutomirski wrote: > On Fri, Apr 24, 2015 at 1:13 PM, Christoph Lameter <cl@linux.com> wrote: > > On Fri, 24 Apr 2015, Andy Lutomirski wrote: > > > >> That's sort of what my patch does -- you need CAP_SETPCAP to switch > >> the securebit. > >> > >> But Christoph's patch required it to add caps to the ambient set, right? > > > > Yes but you seem to be just adding one additional step without too much of > > a benefit because you still need CAP_SETPCAP. > > > > No, because I set the default to on :)
Right - I definately prefer
. default off . CAP_SETPCAP required to turn it on (for self and children) . once on, anyone can copy bits from (whatever we decided) to pA.
> Also, in my model you can do: > > $ sudo capset cap_whatever=eip something > $ ./something > > and the program can make its cap be ambient and run a helper. In the > CAP_SETPCAP model, that doesn't work. > > --Andy > > -- > Andy Lutomirski > AMA Capital Management, LLC > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/
| |