From: Christian Brauner <brauner@kernel.org>
To: "Anton V. Boyarshinov" <boyarsh@altlinux.org>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
ebiederm@xmission.com, legion@kernel.org, ldv@altlinux.org,
linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Christoph Hellwig <hch@lst.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] Add ability to disallow idmapped mounts
Date: Fri, 4 Feb 2022 10:45:15 +0100 [thread overview]
Message-ID: <20220204094515.6vvxhzcyemvrb2yy@wittgenstein> (raw)
In-Reply-To: <20220204065338.251469-1-boyarsh@altlinux.org>
On Fri, Feb 04, 2022 at 09:53:38AM +0300, Anton V. Boyarshinov wrote:
> Idmapped mounts may have security implications [1] and have
> no knobs to be disallowed at runtime or compile time.
>
> This patch adds a sysctl and a config option to set its default value.
>
> [1] https://lore.kernel.org/all/m18s7481xc.fsf@fess.ebiederm.org/
>
> Based on work from Alexey Gladkov <legion@kernel.org>.
>
> Signed-off-by: Anton V. Boyarshinov <boyarsh@altlinux.org>
> ---
Thank your for the general idea, Anton.
If you want to turn off idmapped mounts you can already do so today via:
echo 0 > /proc/sys/user/max_user_namespaces
Aside from that, idmapped mounts can only be created by fully privileged
users on the host for a selected number of filesystems. They can neither
be created as an unprivileged user nor can they be created inside user
namespaces.
I appreciate the worry. Any new feature may have security implications
and bugs. In addition, we did address these allegations multiple times
already (see [1], [2], [3], [4], [5]).
As the author/maintainer of this feature,
Nacked-by: Christian Brauner <brauner@kernel.org>
[1]: https://lore.kernel.org/lkml/20210213130042.828076-1-christian.brauner@ubuntu.com/T/#m3a9df31aa183e8797c70bc193040adfd601399ad
[2]: https://lore.kernel.org/lkml/m1r1ifzf8x.fsf@fess.ebiederm.org
[3]: https://lore.kernel.org/lkml/20210213130042.828076-1-christian.brauner@ubuntu.com/T/#m59cdad9630d5a279aeecd0c1f117115144bc15eb
[4]: https://lore.kernel.org/lkml/20210510125147.tkgeurcindldiwxg@wittgenstein
[5]: https://lore.kernel.org/linux-fsdevel/CAHrFyr4AYi_gad7LQ-cJ9Peg=Gt73Sded8k_ZHeRZz=faGzpQA@mail.gmail.com
next prev parent reply other threads:[~2022-02-04 9:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 6:53 Anton V. Boyarshinov
2022-02-04 9:45 ` Christian Brauner [this message]
2022-02-04 10:26 ` Anton V. Boyarshinov
2022-02-04 15:10 ` Christian Brauner
2022-02-05 7:57 ` Anton V. Boyarshinov
2022-02-05 13:57 ` James Bottomley
2022-02-06 13:47 ` Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220204094515.6vvxhzcyemvrb2yy@wittgenstein \
--to=brauner@kernel.org \
--cc=boyarsh@altlinux.org \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=kernel-hardening@lists.openwall.com \
--cc=ldv@altlinux.org \
--cc=legion@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®