Lines Matching full:mount
18 Non-privileged mount (or user mount):
31 Mount owner:
41 module (fuse.ko), a userspace library (libfuse.*) and a mount utility
55 The filesystem type given to mount(2) can be one of the following:
58 This is the usual way to mount a FUSE filesystem. The first
59 argument of the mount system call may contain an arbitrary string,
64 mount system call is interpreted as the name of the device.
66 Mount options
78 The numeric user id of the mount owner.
81 The numeric group id of the mount owner.
89 'allow_other' mount option.
111 mount -t fusectl none /sys/fs/fuse/connections
146 Only the owner of the mount may read or write these files.
221 Since the mount() system call is a privileged operation, a helper
224 The implication of providing non-privileged mounts is that the mount
228 A) mount owner should not be able to get elevated privileges with the
231 B) mount owner should not get illegitimate access to information from
234 C) mount owner should not be able to induce undesired behavior in
240 A) The mount owner could gain elevated privileges by either:
248 fusermount always adds "nosuid" and "nodev" to the mount options
254 information is otherwise inaccessible to the mount owner, so this
259 C) There are several ways in which the mount owner can induce
262 1) mounting a filesystem over a file or directory which the mount
267 permissions on the mountpoint and only allowing the mount if
268 the mount owner can do unlimited modification (has write
272 2) Even if 1) is solved the mount owner can change the behavior
278 system file, and then accessing a file on the mount owner's
289 monitored or manipulated by the mount owner. Since if the
290 mount owner can ptrace a process, it can do all of the above
291 without using a FUSE mount, the same criteria as used in
296 prevent C/2/i, it is enough to check if mount owner has enough
308 set, the mounting user can add the 'allow_other' mount option which
314 privileged. If any process could access such an 'allow_other' mount