Skip to content
EntityQ1339972· pop 10· linked from 227 articles

EncFS is a Free (LGPL) FUSE-based cryptographic filesystem. It transparently encrypts files, using an arbitrary directory as storage for the encrypted files.

Key facts

Software.name
EncFS
Software.developer
Valient Gough
Software.latest_release_version
1.9.5
Software.discontinued
yes
Software.replaced_by
gocryptfs
Software.operating_system
Linux, FreeBSD, macOS, Windows ("encfs4win" port) (also Safe, an alternative macOS, Windows port) and Android apps
Software.genre
filesystem, encryption
Software.license
LGPL
Software.website
EncFS home

via Wikipedia infobox

Official website

Valient Gough

arg0.net

Link to the official site · 487 chars · not written by Vinony

Source code

EncFS provides an encrypted virtual filesystem. It runs in userspace, using the FUSE library. EncFS is open source software, licensed under the LGPL. EncFS was first released in 2003, making it one of the earlier FUSE filesystems! At the time, there were few options available for Linux, and the kernel modules that were available had not kept pace with Linux development. This meant that every kernel upgrade was likely to break the filesystem until the module was updated. When FUSE became available, I wrote a CFS replacement for my own use and released it to Open Source. EncFS encrypts individual files, by translating all requests for the virtual EncFS filesystem into the equivalent encrypted operations on the raw filesystem. If you're considering setting up a new encrypted filesystem, I'd recommend looking into newer alternatives, such as the excellent GoCryptFS, or else use full-disk encryption when possible. Data has a long lifespan, and people still have data that was encrypted with EncFS. This project has been mostly dormant for years. I've recently begun porting EncFS to Rust as a way to learn Rust, which turned out to be easier than I'd expected with the help of modern-day developer tooling. The old C++ code has been removed. The code can be found in old branches, or old releases, but is not being maintained. Use encfsctl passwd --upgrade to convert an existing filesystem to the V7 config format and switch to the Argon2id key-derivation function. You will be prompted for the current password and a new one. The tool writes a new .encfs7 file; the old config file is left in place. Ensure the volume is not mounted when upgrading. 2. Mount the filesystem with encfs. The first argument is the encrypted root directory (where the config lives), the second is the mount point where you will see plaintext: You can now read and write files under ~/mount ; they are stored encrypted under ~/encrypted . When finished, unmount: The encfsr binary provides reverse encryption: your plaintext files live on disk in a source directory, and encfsr mounts a read-only virtual filesystem that exposes the encrypted view of that directory. Use this when you want to back up or sync an encrypted representation of local data (e.g. to an untrusted or cloud storage) without storing plaintext there. Normal encfs : encrypted dir → mount point shows plaintext (read/write). encfsr : plaintext dir → mount point shows encrypted view (read-only). Requirements A V7 EncFS config (e.g. .encfs7 ). Older configs are not supported. Config should be created without per-file IV headers: use encfsctl new --no-unique-iv ... so the content is deterministic and suitable for reverse mode. Then copy or sync from /mnt/enc to your backup/cloud target; the content and filenames there are encrypted.

Excerpt from the source-code README · 5,452 chars · not written by Vinony

Wikidata facts

Official website
www.arg0.net/encfs
Show 3 more facts
source code repository URL
github.com/vgough/encfs
software version identifier
1.9.5
publication date
2003-00-00
Sources (5)

via Wikidata · CC0

~9 min read

Article

29 sections
Contents
  • Common uses
  • Advantages
  • Cross-platform
  • Bitrot detection
  • Scalable storage
  • Normal file server
  • Different physical devices
  • Faster backup
  • Reduced corruption
  • Optimizations
  • Random file access
  • Disadvantages
  • Compatibility
  • No support for very long filenames
  • General security concerns
  • EncFS 1.7 security concerns
  • EncFS 1.8 security concerns
  • Filesystem options
  • Cipher algorithm
  • Block size
  • Filename encoding
  • Filename IV chaining
  • Per-file IV initialization vector
  • External IV chaining
  • Filename to IV header chaining
  • Block MAC headers
  • See also
  • References
  • External links

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.

Available in 10 languages

via Wikidata sitelinks · CC0

Connections

Categories