-
Notifications
You must be signed in to change notification settings - Fork 76
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
relaxed_permissions not working on Ubuntu 22.04 #121
Comments
I just updated one of my systems yesterday night, will test it in the evening today. |
please try again with the current (3.1 as of now) version, thanks! |
Hello! Tried with the latest version, but unfortunately the situation is unchanged. unionfs-fuse version: 3.2 Bye |
It actually works as expected and would be unsual if not - this is a kernel fuse feature - by default we add in "default_permissions", which makes the kernel to verify if you are allowed to access a file. "relaxed_permissions" removes "default_permissions", unless started as root, this option is then ignored for security reasons. Example
Other shell:
Other shell:
and this creates
Hence, the feature works as expected. |
Hello!
I use the Unionfs-fuse solution to separate static data from data generated during the game (save, score, setting, etc.) for games running over an emulator. In the past, there was a problem that caused the file created when writing to union to get stuck in the permission check (it was virtually 0 bytes in size and no permission bits were set to it (000)). This is solved by the "relaxed_permissions" option. Unfortunately, the problem came back when I switched to the latest Ubuntu release, 22.04. It's like the "relaxed_permissions" option doesn't work for some reason. Can you see what the problem might be? If you write what data you need I will try to provide it. Until then:
unionfs-fuse version: 2.3
(compiled with xattr support)
FUSE library version 3.10.5
using FUSE kernel interface version 7.31
fusermount3 version: 3.10.5
Thanks
The text was updated successfully, but these errors were encountered: