Purpose of the fuse group
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fuse (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
In Jaunty, users are no longer added to the fuse group by default.
This causes error messages like this when one attempts to use fuse:
$ python /usr/share/
fusermount: failed to open /etc/fuse.conf: Permission denied
fusermount: option allow_other only allowed if 'user_allow_other' is set in /etc/fuse.conf
Traceback (most recent call last):
File "/usr/share/
main()
File "/usr/share/
server.main()
File "/usr/lib/
main(**d)
fuse.FuseError: filesystem initialization failed
Note, however that it is still possible to use fuse filesystems. In some cases the error message is shown and the mount proceeds anyway, while in others even the error message is hidden:
$ groups
nikratio adm dialout cdrom plugdev lpadmin admin sambashare
$ ls tmp/
$ python /usr/share/
$ ls tmp
hello
$ fusermount -u tmp
I think something is wrong with this. If users do not need to be in the fuse group to use fuse, why is /etc/fuse.conf only readable by members of this group? Or, putting it the other way around, why am I allowed to use fuse if I'm not in the fuse group?
This may or may not be related to bug #339889 (I don't quite understand the last comment and why it was set to invalid).
I experienced the same behavior yesterday. Is the read-permission only to members of the fuse-group the only restriction that prohibits users from using fuse? Usually I'd say fuse.conf should be readable to anyone as most other config-files in /etc ...
Why are users not placed into the fuse-group anymore?