Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966265AbbBCPzs (ORCPT ); Tue, 3 Feb 2015 10:55:48 -0500 Received: from h2.hallyn.com ([78.46.35.8]:42244 "EHLO h2.hallyn.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965999AbbBCPzp (ORCPT ); Tue, 3 Feb 2015 10:55:45 -0500 Date: Tue, 3 Feb 2015 16:55:44 +0100 From: "Serge E. Hallyn" To: Christoph Lameter 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 Message-ID: <20150203155544.GE2923@mail.hallyn.com> References: <20150202171257.GD24351@ubuntumail> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1638 Lines: 35 Quoting Christoph Lameter (cl@linux.com): > On Mon, 2 Feb 2015, Serge Hallyn wrote: > > > A key concept behind posix capabilities is that the privilege comes from > > both the person and the file being executed. As you say below basically > > anything can be executed by the program so that is completely violated. > > Well this patch does not change that. Its just that the file being > executed can inherit the parent caps without having to set caps in the new > executable. > > > Still, it's not that different from mmapping some arbitrary code and > > jumping into it whlie retaining caps. > > Owww. Thats a pretty far jump from what this patch does. Hm? That's not something about a kernel patch - it's just something you can do in userspace today to not lose your privilege in several mac systems. > > Not saying this is a good idea necessarily, but worth thinking about. > > Well we keep on having actual problems with caps for long years now. We > need a solution. This means a patch that solves the issue. 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. -- 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/