[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D1BBFWKGIA94.JP53QNURY3J4@kernel.org>
Date: Thu, 16 May 2024 22:29:06 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Casey Schaufler" <casey@...aufler-ca.com>, "Jonathan Calmels"
<jcalmels@...0.net>, <brauner@...nel.org>, <ebiederm@...ssion.com>, "Luis
Chamberlain" <mcgrof@...nel.org>, "Kees Cook" <keescook@...omium.org>,
"Joel Granados" <j.granados@...sung.com>, "Serge Hallyn"
<serge@...lyn.com>, "Paul Moore" <paul@...l-moore.com>, "James Morris"
<jmorris@...ei.org>, "David Howells" <dhowells@...hat.com>
Cc: <containers@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>, <linux-security-module@...r.kernel.org>,
<keyrings@...r.kernel.org>
Subject: Re: [PATCH 0/3] Introduce user namespace capabilities
On Thu May 16, 2024 at 10:07 PM EEST, Casey Schaufler wrote:
> I suggest that adding a capability set for user namespaces is a bad idea:
> - It is in no way obvious what problem it solves
> - It is not obvious how it solves any problem
> - The capability mechanism has not been popular, and relying on a
> community (e.g. container developers) to embrace it based on this
> enhancement is a recipe for failure
> - Capabilities are already more complicated than modern developers
> want to deal with. Adding another, special purpose set, is going
> to make them even more difficult to use.
What Inh, Prm, Eff, Bnd and Amb is not dead obvious to you? ;-)
One UNs cannot hurt...
I'm not following containers that much but didn't seccomp profiles
supposed to be the silver bullet?
BR, Jarkko
Powered by blists - more mailing lists