From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [RFC] capabilities: Ambient capabilities Date: Fri, 24 Apr 2015 13:18:44 -0700 Message-ID: References: <20150424175348.GL16377@ubuntumail> <20150424190935.GN16377@ubuntumail> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Christoph Lameter Cc: Serge Hallyn , Jarkko Sakkinen , Andrew Lutomirski , Ted Ts'o , Andrew Morton , "Andrew G. Morgan" , Linux API , Mimi Zohar , Michael Kerrisk , Austin S Hemmelgarn , linux-security-module , Aaron Jones , Serge Hallyn , LKML , Markku Savela , Kees Cook , Jonathan Corbet List-Id: linux-api@vger.kernel.org On Fri, Apr 24, 2015 at 1:13 PM, Christoph Lameter 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 :) 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