Date: Sun, 6 Feb 2022 14:47:41 +0100 From: Christian Brauner <brauner@...nel.org> To: "Anton V. Boyarshinov" <boyarsh@...linux.org> Cc: viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org, ebiederm@...ssion.com, legion@...nel.org, ldv@...linux.org, linux-kernel@...r.kernel.org, kernel-hardening@...ts.openwall.com, Christoph Hellwig <hch@....de>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [PATCH] Add ability to disallow idmapped mounts On Sat, Feb 05, 2022 at 10:57:58AM +0300, Anton V. Boyarshinov wrote: > В Fri, 4 Feb 2022 16:10:32 +0100 > Christian Brauner <brauner@...nel.org> пишет: > > > > > It turns off much more than idmapped mounts only. More fine grained > > > control seems better for me. > > > > If you allow user namespaces and not idmapped mounts you haven't reduced > > your attack surface. > > I have. And many other people have. People who have creating user > namespaces by unpriviliged user disabled. I find it sad that we have no > tool in mainline kernel to limit users access to creating user > namespaces except complete disabling them. But many distros have that > tools. Different tools with different interfaces and semantics :( > > And at least one major GNU/Linux distro disabled idmapped mounts > unconditionally. If I were the author of this functionality, I would > prefer to have a knob then have it unavailible for for so many users. But as you wish. You're talking about the author of the allegations being involved in disabling idmapped mounts for rhel under  as I was told. If a downstream distro wants to disable this feature based on allegations we've refuted multiple times then we can't stop them from doing so. The only disconcerting thing is that this helps spreads misinformation as evidenced by this patch. The allegations and refutation around them are all visible and I've linked to them in the initial reply. This is a root-only accessible feature with a massive testsuite and being used for 2 years. Each bug fixed gets its own regression test right away. We will of course take and upstream patches that fix actual clearly reported bugs. In the end it is not different from say Archlinux  having had user namespaces disabled for 5+ years from their introduction in 2013 onwards and many other examples. Downstream distros can make whatever choice they want and diverge from upstream. In any case, I'll be on vacation for about 2 weeks with very limited access to internet going forward. : https://bugs.archlinux.org/task/36969 : https://gitlab.com/redhat/centos-stream/src/kernel/centos-stream-9/-/merge_requests/131 > > > An unprivileged user can reach much more > > exploitable code simply via unshare -user --map-root -mount which we > > still allow upstream without a second thought even with all the past and > > present exploits (see > > https://www.openwall.com/lists/oss-security/2022/01/29/1 for a current > > one from this January). > > > > > > > > > They can neither > > > > be created as an unprivileged user nor can they be created inside user > > > > namespaces. > > > > > > But actions of fully privileged user can open non-obvious ways to > > > privilege escalation. > > > > A fully privileged user potentially being able to cause issues is really > > not an argument; especially not for a new sysctl. > > You need root to create idmapped mounts and you need root to turn off > > the new knob. > > > > It also trivially applies to a whole slew of even basic kernel tunables > > basically everything that can be reached by unprivileged users after a > > privileged user has turned it on or configured it. > > > > After 2 years we haven't seen any issue with this code and while I'm not > > promising that there won't ever be issues - nobody can do that - the > > pure suspicion that there could be some is not a justification for > > anything. > >
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.