Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966382AbbBCRSS (ORCPT ); Tue, 3 Feb 2015 12:18:18 -0500 Received: from resqmta-ch2-12v.sys.comcast.net ([69.252.207.44]:58487 "EHLO resqmta-ch2-12v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965775AbbBCRSN (ORCPT ); Tue, 3 Feb 2015 12:18:13 -0500 Date: Tue, 3 Feb 2015 11:18:11 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: "Serge E. Hallyn" cc: Serge Hallyn , Serge Hallyn , Andy Lutomirski , Jonathan Corbet , Aaron Jones , "Ted Ts'o" , linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org, akpm@linuxfoundation.org, morgan@kernel.org Subject: Re: [capabilities] Allow normal inheritance for a configurable set of capabilities In-Reply-To: <20150203155544.GE2923@mail.hallyn.com> Message-ID: References: <20150202171257.GD24351@ubuntumail> <20150203155544.GE2923@mail.hallyn.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 814 Lines: 18 On Tue, 3 Feb 2015, Serge E. Hallyn wrote: > We've currently got two proposals. (Three includig yours; but I explained my > problem with yours earlier this morning - do appreciate the proposal and > the patch though, really, thanks) It's worth digging into the details of > each, but if they end up complicating things then perhaps "dropping > capabilities and going with something new" ought to be another proposal. Ok that is about the binding to a person and executable? So you think there should be a cap_inheritable mask settable in the caps of each file. -- 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/