diff options
| author | Przemysław Pawełczyk <przemoc@gmail.com> | 2016-11-29 06:33:14 +0100 |
|---|---|---|
| committer | Nikolaus Rath <Nikolaus@rath.org> | 2016-11-28 21:33:14 -0800 |
| commit | dfbfee07abc9329715a12ce251e0ceeda8d78f19 (patch) | |
| tree | 44015341e5c1fe85631d710768a88352efaad71c /doc/kernel.txt | |
| parent | 4fdf83f4dd2b0c3a0688d23de23ad953abf473ac (diff) | |
| download | libfuse-dfbfee07abc9329715a12ce251e0ceeda8d78f19.tar.gz | |
Rename more things from fuse to fuse3
Diffstat (limited to 'doc/kernel.txt')
| -rw-r--r-- | doc/kernel.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/kernel.txt b/doc/kernel.txt index 7938aab..e73484f 100644 --- a/doc/kernel.txt +++ b/doc/kernel.txt @@ -39,7 +39,7 @@ What is FUSE? FUSE is a userspace filesystem framework. It consists of a kernel module (fuse.ko), a userspace library (libfuse.*) and a mount utility -(fusermount). +(fusermount3). One of the most important features of FUSE is allowing secure, non-privileged mounts. This opens up new possibilities for the use of @@ -176,7 +176,7 @@ How do non-privileged mounts work? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Since the mount() system call is a privileged operation, a helper -program (fusermount) is needed, which is installed setuid root. +program (fusermount3) is needed, which is installed setuid root. The implication of providing non-privileged mounts is that the mount owner must not be able to use this capability to compromise the @@ -204,7 +204,7 @@ How are requirements fulfilled? The solution is not to allow opening device files and ignore setuid and setgid bits when executing programs. To ensure this - fusermount always adds "nosuid" and "nodev" to the mount options + fusermount3 always adds "nosuid" and "nodev" to the mount options for non-privileged mounts. B) If another user is accessing files or directories in the @@ -222,7 +222,7 @@ How are requirements fulfilled? owner could otherwise not be able to modify (or could only make limited modifications). - This is solved in fusermount, by checking the access + This is solved in fusermount3, by checking the access permissions on the mountpoint and only allowing the mount if the mount owner can do unlimited modification (has write access to the mountpoint, and mountpoint is not a "sticky" |