Thread (9 messages) 9 messages, 2 authors, 2d ago

Re: [PATCH 1/2] fuse: allow FUSE_SYNCFS for privileged userspace servers

From: Jimmy Zuber <hidden>
Date: 2026-06-19 16:33:51
Also in: fuse-devel, linux-fsdevel, linux-kselftest, lkml

On Mon, 16 Jun 2026, Miklos Szeredi [off-list ref] wrote:
Sounds really easy to trick: start the server in the initial user ns,
then clone the mounter with a new user/mount namespace.   The
init_user_ns test will pass happily, since the server is running in
the initial namespace.
Ah, the intention was to limit sync to sufficiently privileged FUSE
setups.  I missed that the initial user namespace is not equivalent to
elevated permissions.  I am thinking instead it would make sense to
assert that the opener of /dev/fuse has CAP_SYS_ADMIN in the initial
user namespace.  They could then hand off the fd to a less privileged
server, but that is the prerogative of that privileged user, so I think
it satisfies the spirit of the DoS prevention requirement.

I will follow up shortly with a new version.

Thank you!

Jimmy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help