Bug#725706: gvfs-fuse: make gvfs-fuse work out of the box

[Laurent Bigonville]

Le Mon, 07 Oct 2013 18:58:58 +0200,
Michael Biebl <biebl at debian.org> a écrit :

> The following worked for me:
> 1/ sudo chown root:fuse /usr/lib/gvfs/gvfsd-fuse
> 2/ sudo chmod 2755 /usr/lib/gvfs/gvfsd-fuse
> 3/ echo 'KERNEL=="fuse", TAG+="uaccess"' >
> /etc/udev/rules.d/61-fuse-permissions.rules

I probably don't have the full picture here, but what's the difference
with the default upstream fuse permissions? Users will endup with the
ability to read/write to /dev/fuse and gvfsd-fuse will allow them to
mount $any fs, if I'm not wrong.

I'm just wondering what's the benefit of diverging from upstream
behavior and the other distributions (I'm aware this might be
considered as an authority argument but I'm trying to understand what
we are trying to achieve this going this way).

> Without 3/, I got a permission denied error from fusermount:
> $ /usr/lib/gvfs/gvfsd-fuse -d -f /run/user/1000/gvfs-fuse/
> fusermount: failed to open /dev/fuse: Permission denied

Quickly looking at the fusercode it seems it's dropping its privileges
at some point.

Cheers

Laurent Bigonville