[patch 7/9] unprivileged mounts: allow unprivileged fuse mounts
miklos at szeredi.hu
Tue Jan 8 14:42:20 PST 2008
> On Tue 2008-01-08 12:35:09, Miklos Szeredi wrote:
> > From: Miklos Szeredi <mszeredi at suse.cz>
> > Use FS_SAFE for "fuse" fs type, but not for "fuseblk".
> > FUSE was designed from the beginning to be safe for unprivileged users. This
> > has also been verified in practice over many years. In addition unprivileged
> Eh? So 'kill -9 no longer works' and 'suspend no longer works' is not
> considered important enough to even mention?
No. Because in practice they don't seem to matter. Also because
there's no way in which fuse could be done differently to address
The 'kill -9' thing is basically due to VFS level locking not being
interruptible. It could be changed, but I'm not sure it's worth it.
For the suspend issue, there are also no easy solutions.
> 'updatedb no longer works' is not a problem?
I haven't seen any problems with updatedb, and haven't had any bug
reports about it either.
> Are you ready to offer shell account for bugtraq people to see how
> long it survives?
Bugtraq people are free to install fuse on their machines and take it
AFAIR there were two security vulnerabilities in fuse's history, one
of them an information leak in the kernel module, and the other one an
mtab corruption issue in the fusermount utility. I don't think this
is such a bad track record.
More information about the Containers