From mboxrd@z Thu Jan 1 00:00:00 1970 From: Serge Hallyn Subject: Re: [RFC] capabilities: Ambient capabilities Date: Fri, 24 Apr 2015 19:09:35 +0000 Message-ID: <20150424190935.GN16377@ubuntumail> References: <20150424175348.GL16377@ubuntumail> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Lutomirski Cc: Christoph Lameter , 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 Quoting Andy Lutomirski (luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org): > On Fri, Apr 24, 2015 at 10:53 AM, Serge Hallyn wrote: > > Quoting Christoph Lameter (cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org): > >> On Thu, 9 Apr 2015, Christoph Lameter wrote: > >> > >> > > I'll submit a new version this week with the securebits. Sorry for the delay. > >> > Are we going to get a new version? > >> > >> Replying to my own here. Cant we simply use the SETPCAP approach as per > >> the patch I posted? > > > > Andy had objections to that, but it seems ok to me. > > > > I object because CAP_SETPCAP is very powerful whereas > CAP_NET_BIND_SERVICE, for example, isn't. I'm fine with having a > switch to turn off ambient caps, but requiring the "on" state to give Would only really be needed for the initial 'enable ambient caps for this process tree', though. Once that was set, add/remove'ing caps from the ambient set wouldn't need to be required. > processes superpowers seems unfortunate. > > Sorry for the huge delay. I got caught up with travel and the merge > window. Here's a sneak peek: > > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=cap_ambient > > I need to write the user code to go with it and test it a bit before > sending it out for real. Ok, thanks -serge