Developer(s) | Valient Gough |
---|---|
Stable release |
1.9.1 / September 18, 2016
|
Repository | github |
Operating system | Linux, FreeBSD, macOS,Windows ("encfs4win" port) (also Safe, an alternative macOS and Windows port) |
Type | filesystem, encryption |
License | LGPL |
Website | EncFS home |
EncFS is a Free (LGPL) FUSE-based cryptographic filesystem. It transparently encrypts files, using an arbitrary directory as storage for the encrypted files.
Two directories are involved in mounting an EncFS filesystem: the source directory, and the mountpoint. Each file in the mountpoint has a specific file in the source directory that corresponds to it. The file in the mountpoint provides the unencrypted view of the one in the source directory. Filenames are encrypted in the source directory.
Files are encrypted using a volume key, which is stored either within or outside the encrypted source directory. A password is used to decrypt this key.
EncFS offers several advantages over other disk encryption software simply because each file is stored individually as an encrypted file somewhere else in the host's directory tree.
EncFS is available on multiple platforms, whereas eCryptfs is tied to the Linux kernel
EncFS implements bitrot detection on top of any underlying filesystem
EncFS has no "volumes" that occupy a fixed size — encrypted directories grow and shrink as more files are added to or removed from the mountpoint
EncFS's encrypted directory can be located on a normal file server (via NFS, SSHFS, etc.) and can be mirrored and backed up efficiently with normal file-system tools, such as Rsync
It is possible for some directories on the mountpoint to exist on different physical devices, if a filesystem is mounted over one of the sub-directories in the source directory
Backup utilities can back up only the files that have changed in the source directory (file synchronisation, cloud storage)
Corruption of data is more isolated. Corruption of filedata is local to a single file, and data corruption of the filesystem can be corrected with a reliable filesystem repair utility like fsck. Some whole-disk encryption systems lack one or both of these attributes.