From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758569AbbDXTZv (ORCPT ); Fri, 24 Apr 2015 15:25:51 -0400 Received: from resqmta-ch2-03v.sys.comcast.net ([69.252.207.35]:38036 "EHLO resqmta-ch2-03v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758541AbbDXTZs (ORCPT ); Fri, 24 Apr 2015 15:25:48 -0400 Date: Fri, 24 Apr 2015 14:25:46 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Serge Hallyn cc: Andy Lutomirski , 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 Subject: Re: [RFC] capabilities: Ambient capabilities In-Reply-To: <20150424190935.GN16377@ubuntumail> Message-ID: References: <20150424175348.GL16377@ubuntumail> <20150424190935.GN16377@ubuntumail> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 24 Apr 2015, Serge Hallyn wrote: > > 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. Exactly. Its much simpler than alternate approaches. And its convoluted enough.