From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753982AbbCMSw3 (ORCPT ); Fri, 13 Mar 2015 14:52:29 -0400 Received: from resqmta-ch2-01v.sys.comcast.net ([69.252.207.33]:33489 "EHLO resqmta-ch2-01v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751406AbbCMSw0 (ORCPT ); Fri, 13 Mar 2015 14:52:26 -0400 Date: Fri, 13 Mar 2015 13:52:23 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Andy Lutomirski cc: "Andrew G. Morgan" , Andrew Lutomirski , Kees Cook , Serge Hallyn , Jonathan Corbet , Aaron Jones , "Ted Ts'o" , linux-security-module , LKML , Linux API , Andrew Morton , Mimi Zohar , Austin S Hemmelgarn , Markku Savela , Jarkko Sakkinen , Michael Kerrisk Subject: Re: [RFC] capabilities: Ambient capabilities In-Reply-To: Message-ID: References: <933931146caf5dac58379f50c017bff9f6c47661.1426183417.git.luto@kernel.org> 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, 13 Mar 2015, Andy Lutomirski wrote: > > The functionalty here depends on CAP_SETPCAP. That was intended as some > > point to be off by default? You can have distros/kernels with that being > > off. > > Not in my version. I don't want to further encourage people to hand > out CAP_SETPCAP. Owww... But if you leave it in then maybe Andrew will be satisfied with this approach?