From: Christian Brauner <brauner@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Dave Marchevsky <davemarchevsky@fb.com>,
linux-fsdevel@vger.kernel.org,
Seth Forshee <sforshee@digitalocean.com>,
Rik van Riel <riel@surriel.com>, kernel-team <kernel-team@fb.com>,
Andrii Nakryiko <andrii@kernel.org>, Chris Mason <clm@fb.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] fuse: allow CAP_SYS_ADMIN in root userns to access allow_other mount
Date: Tue, 24 May 2022 17:44:55 +0200 [thread overview]
Message-ID: <20220524154455.khecrq5ra5olj7am@wittgenstein> (raw)
In-Reply-To: <CAJfpeguOHRtmWTuQfUT_Lb98ddiyzZcjk=D8WyyYA8i923-Lag@mail.gmail.com>
On Tue, May 24, 2022 at 09:07:34AM +0200, Miklos Szeredi wrote:
> On Tue, 24 May 2022 at 06:36, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> > I still think that tools like perf being able to provide good tracing
> > data is going to hurt due to this cautious rejection of access, but
> > with Kconfig we at least give an option for users to opt out of it.
> > WDYT?
>
> I'd rather use a module option for this, always defaulting to off .
> Then sysadmin then can choose to turn this protection off if
> necessary. This would effectively be the same as "user_allow_other"
> option in /etc/fuse.conf, which fusermount interprets but the kernel
> doesn't.
Agreed. Should be properly documented.
Christian
prev parent reply other threads:[~2022-05-24 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 22:11 [PATCH] fuse: allow CAP_SYS_ADMIN in root userns to access allow_other mount Dave Marchevsky
2021-11-12 2:10 ` Rik van Riel
2021-11-12 10:13 ` Christian Brauner
2021-11-12 23:29 ` Dave Marchevsky
2021-11-15 15:28 ` Miklos Szeredi
2022-05-17 16:50 ` Dave Marchevsky
2022-05-18 11:22 ` Christian Brauner
2022-05-18 11:26 ` Miklos Szeredi
2022-05-19 4:56 ` Andrii Nakryiko
2022-05-19 8:59 ` Christian Brauner
2022-05-24 4:35 ` Andrii Nakryiko
2022-05-24 7:07 ` Miklos Szeredi
2022-05-24 14:59 ` Rik van Riel
2022-05-24 15:44 ` Christian Brauner [this message]
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=20220524154455.khecrq5ra5olj7am@wittgenstein \
--to=brauner@kernel.org \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=clm@fb.com \
--cc=davemarchevsky@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=riel@surriel.com \
--cc=sforshee@digitalocean.com \
/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;
as well as URLs for NNTP newsgroup(s).