mirrors/libfuse
0
0
Fork 0
mirror of https://github.com/libfuse/libfuse.git synced 2024-11-23 12:14:15 +08:00
Code Issues Packages Projects Releases Wiki Activity
1,248 Commits 14 Branches 142 Tags 10 MiB
C 83.5%
C++ 9.1%
Python 4.6%
Meson 1.6%
Shell 1.2%
30243ca7ad
Go to file
Nikolaus Rath 30243ca7ad Accept zero value for fuse_conn_info options 
This may not make sense for all options, but it's good practice.
2016-10-20 14:04:37 -07:00
doc mount.fuse(8): remove max_readahead, max_write, [a]sync_read 2016-10-20 14:04:37 -07:00
example Make --help output more suitable for end-user 2016-10-15 19:46:57 -07:00
include Removed all "Introduced in..." comments 2016-10-20 14:04:37 -07:00
lib Accept zero value for fuse_conn_info options 2016-10-20 14:04:37 -07:00
test Unify handling of fuse_conn_info options 2016-10-15 16:49:23 -07:00
util Removed -o nonempty option 2016-10-15 18:53:45 -07:00
.dir-locals.el Added basic unit tests. 2016-03-29 16:06:29 -07:00
.gitignore Ignore GNU Global tag files. 2016-10-16 19:51:40 -07:00
.travis.yml Travis: use "make test" instead of calling pytest directly 2016-10-13 11:02:04 -07:00
AUTHORS Released 3.0.0pre0 2016-10-03 09:08:58 -07:00
ChangeLog.rst Spelling fix 2016-10-17 20:15:25 -07:00
configure.ac Renamed some examples to make their function more obvious 2016-10-09 22:03:07 -07:00
COPYING Update COPYING* 2011-05-26 15:36:35 +02:00
COPYING.LIB Update COPYING* 2011-05-26 15:36:35 +02:00
fuse3.pc.in "pkg-config fuse3 --libs" gives the wrong library name 2013-12-11 15:43:45 +01:00
makeconf.sh Update makeconf.sh 2016-01-14 12:27:15 -08:00
Makefile.am tests: use freshly-build fusermount (instead of system version) 2016-10-13 11:02:04 -07:00
README.md Various documentation updates 2016-10-16 15:12:29 -07:00

README.md

libfuse

Warning: unresolved security issue

Be aware that FUSE has an unresolved security bug (bug #15): if the default_permissions mount option is not used, the results of the first permission check performed by the file system for a directory entry will be re-used for subsequent accesses as long as the inode of the accessed entry is present in the kernel cache - even if the permissions have since changed, and even if the subsequent access is made by a different user.

This bug needs to be fixed in the Linux kernel and has been known since 2006 but unfortunately no fix has been applied yet. If you depend on correct permission handling for FUSE file systems, the only workaround is to use default_permissions (which does not currently support ACLs), or to completely disable caching of directory entry attributes. Alternatively, the severity of the bug can be somewhat reduced by not using the allow_other mount option.

About

FUSE (Filesystem in Userspace) is an interface for userspace programs to export a filesystem to the Linux kernel. The FUSE project consists of two components: the fuse kernel module (maintained in the regular kernel repositories) and the libfuse userspace library (maintained in this repository). libfuse provides the reference implementation for communicating with the FUSE kernel module.

A FUSE file system is typically implemented as a standalone application that links with libfuse. libfuse provides functions to mount the file system, unmount it, read requests from the kernel, and send responses back. libfuse offers two APIs: a "high-level", synchronous API, and a "low-level" asynchronous API. In both cases, incoming requests from the kernel are passed to the main program using callbacks. When using the high-level API, the callbacks may work with file names and paths instead of inodes, and processing of a request finishes when the callback function returns. When using the low-level API, the callbacks must work with inodes and responses must be sent explicitly using a separate set of API functions.

Installation

You can download libfuse from https://github.com/libfuse/libfuse/releases. After extracting the tarball, build and install with

./configure
make -j8
make install

To run some self tests, you need a Python 3 environment with the py.test module installed. To run the tests, execute

python3 -m pytest test/

You may also need to add /usr/local/lib to /etc/ld.so.conf and/or run ldconfig. If you're building from the git repository (instead of using a release tarball), you also need to run ./makeconf.sh to create the configure script.

You'll also need a fuse kernel module (Linux kernels 2.6.14 or later contain FUSE support).

Security implications

If you run make install, the fusermount program is installed set-user-id to root. This is done to allow normal users to mount their own filesystem implementations.

There must however be some limitations, in order to prevent Bad User from doing nasty things. Currently those limitations are:

  • The user can only mount on a mountpoint, for which it has write permission

  • The mountpoint is not a sticky directory which isn't owned by the user (like /tmp usually is)

  • No other user (including root) can access the contents of the mounted filesystem (though this can be relaxed by allowing the use of the allow_other and allow_root mount options in fuse.conf)

Building your own filesystem

FUSE comes with several example file systems in the examples directory. For example, the passthrough examples mirror the contents of the root directory under the mountpoint. Start from there and adapt the code!

The documentation of the API functions and necessary callbacks is mostly contained in the files include/fuse.h (for the high-level API) and include/fuse_lowlevel.h (for the low-level API). An autogenerated html version of the API is available in the doc/html directory and at http://libfuse.github.io/doxygen.

Getting Help

If you need help, please ask on the fuse-devel@lists.sourceforge.net mailing list (subscribe at https://lists.sourceforge.net/lists/listinfo/fuse-devel).

Please report any bugs on the GitHub issue tracker at https://github.com/libfuse/libfuse/issues.