Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AllowRoot doesn't work #144

Closed
Jille opened this issue Jun 27, 2016 · 6 comments
Closed

AllowRoot doesn't work #144

Jille opened this issue Jun 27, 2016 · 6 comments

Comments

@Jille
Copy link

Jille commented Jun 27, 2016

I'm getting this error:
2016/06/27 00:52:21 mount helper error: fusermount: mount failed: Invalid argument

According to https://sourceforge.net/p/fuse/mailman/message/34133833/ allow_root is supposed to be changed into allow_other internally and handled by denying everyone but the user and root in the daemon.

@tv42
Copy link
Member

tv42 commented Jun 27, 2016

Well, crap. Have I mentioned how much I hate the C FUSE library and it's documentation?

I think what will happen next is that I remove the AllowRoot option, and if you want that behavior you use AllowOther and test the Uid field in incoming requests. You can start programming that way right now ;)

I have no intention of letting the Go library bloat into the level of confusion the C library has; we're gonna stick to the kernel API much more closely.

@tv42
Copy link
Member

tv42 commented Jul 1, 2016

The plot thickens. OSXFUSE does allow_root in kernelspace: https://github.com/osxfuse/kext/blob/defa977858140237f9da32205849a91199601b49/osxfuse/fuse_vfsops.c#L268-L272

It's really unclear how to write anything portable when nothing works the same way :(

@omani
Copy link

omani commented Aug 23, 2017

I think what will happen next is that I remove the AllowRoot option, and if you want that behavior you use AllowOther and test the Uid field in incoming requests. You can start programming that way right now ;)

^ this is how I do it btw.

I don't use AllowRoot, AllowOther should do the job for you.

@tv42 tv42 closed this as completed in e0b8970 Jan 17, 2020
ncw added a commit to rclone/rclone that referenced this issue Feb 25, 2020
ncw added a commit to rclone/rclone that referenced this issue Feb 26, 2020
ncw added a commit to rclone/rclone that referenced this issue Feb 26, 2020
@avmaksimov
Copy link

Yeee... AllowOther works fine but before you have to uncomment "user_allow_other” option in /etc/fuse.conf .

@ethicnology
Copy link

Hey fellows, I'm facing the same issue, i want to mount something for the mounting user + root (only) should have access.

I'm a bit lost regarding this history do i have to --allow-other in the rclone command or removing user_allow_orther and add AllowOther in the /etc/fuse.conf

… or something else?

@tv42
Copy link
Member

tv42 commented Aug 1, 2023

If you want to tell the kernel to allow other users to use the mount, you need AllowOther.

If you want to limit which other users can do that, you need to implement that in the filesystem logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants