[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1502030920050.6059@gentwo.org>
Date: Tue, 3 Feb 2015 09:23:12 -0600 (CST)
From: Christoph Lameter <cl@...ux.com>
To: Serge Hallyn <serge.hallyn@...ntu.com>
cc: Serge Hallyn <serge.hallyn@...onical.com>,
Andy Lutomirski <luto@...capital.net>,
Jonathan Corbet <corbet@....net>,
Aaron Jones <aaronmdjones@...il.com>, Ted Ts'o <tytso@....edu>,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, akpm@...uxfoundation.org,
morgan@...nel.org
Subject: Re: [capabilities] Allow normal inheritance for a configurable set
of capabilities
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.
> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists