linux-kernel - Re: [PATCH 1/3] capabilities: user namespace capabilities

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <878r08brmp.fsf@email.froward.int.ebiederm.org>
Date: Fri, 17 May 2024 06:32:46 -0500
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Jonathan Calmels <jcalmels@...0.net>
Cc: brauner@...nel.org,  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>,  Jarkko
 Sakkinen <jarkko@...nel.org>,  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 1/3] capabilities: user namespace capabilities

Jonathan Calmels <jcalmels@...0.net> writes:

> Attackers often rely on user namespaces to get elevated (yet confined)
> privileges in order to target specific subsystems (e.g. [1]). Distributions
> have been pretty adamant that they need a way to configure these, most of
> them carry out-of-tree patches to do so, or plainly refuse to enable
> them.

Pointers please?

That sentence sounds about 5 years out of date.

Eric