From 77dee679eb39dc21c2cc9400e846b5c49292d2e3 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Thu, 16 Mar 2017 10:47:26 -0700 Subject: [PATCH] Document that -o auto_unmount implies -o nodev,nosuid See also issue #148. --- ChangeLog.rst | 1 + doc/mount.fuse.8 | 4 ++++ 2 files changed, 5 insertions(+) diff --git a/ChangeLog.rst b/ChangeLog.rst index 2cabd7d..7b7e3c0 100644 --- a/ChangeLog.rst +++ b/ChangeLog.rst @@ -3,6 +3,7 @@ libfuse 3.1.0 (UNRELEASED) * Re-introduced examples/null.c. * Added experimental support for building with Meson. +* Document that -o auto_unmount implies -o nodev,nosuid. libfuse 3.0.0 (2016-12-08) ========================== diff --git a/doc/mount.fuse.8 b/doc/mount.fuse.8 index c42894b..8020c46 100644 --- a/doc/mount.fuse.8 +++ b/doc/mount.fuse.8 @@ -146,6 +146,10 @@ responsible for releasing the mountpoint, which means that the mountpoint becomes inaccessible if the filesystem terminates without first unmounting. +At the moment, this option implies that the filesystem will also be +mounted with \fBnodev\fP and \fBnosuid\fP (even when mounted by +root). This restriction may be lifted in the future. + .SS "High-level mount options:" These following options are not actually passed to the kernel but interpreted by libfuse. They can only be specified for filesystems -- 2.30.2