EncFS: an Encrypted Filesystem for FUSE.
Go to file
2015-08-16 20:34:42 -07:00
ci add circle.yml 2015-06-19 00:02:44 -07:00
cmake cleanup fuse search path specification 2015-06-16 08:03:02 -07:00
drone-config add drone-config files, for setting up a standalone drone instance 2015-06-15 20:25:29 -07:00
encfs add xattr translation 2015-08-16 20:34:42 -07:00
intl 1.x: update gettext, replace autosprintf with boost::format 2013-11-13 06:45:46 +00:00
po xgettext: Use --no-location to reduce diff noise 2015-03-29 18:28:59 +02:00
tests add test target 2015-06-15 23:48:14 -07:00
.clang-format reformat using clang 2014-10-18 19:19:33 -07:00
.drone.yml add encfsctl check to drone build 2015-06-19 00:02:44 -07:00
.gitignore drop autoconf ignore rules 2015-06-16 20:41:50 -07:00
AUTHORS Import version 1.4.0 2008-01-07 08:09:04 +00:00
ChangeLog Bump version to 1.8.2 2015-03-29 18:50:22 +02:00
circle.yml add circle.yml 2015-06-19 00:02:44 -07:00
CMakeLists.txt change minimum cmake requirement to 3.1, for C++11 support 2015-06-18 08:50:55 -07:00
config.h.cmake drop checks for tr1 headers that are not used 2015-06-17 20:46:46 -07:00
COPYING apply license change 2012-10-22 05:30:55 +00:00
COPYING.GPL apply license change 2012-10-22 05:30:55 +00:00
COPYING.LGPL apply license change 2012-10-22 05:30:55 +00:00
DESIGN.md Fix pod links in DESIGN.md 2015-02-27 21:10:12 -08:00
devmode add cmake config 2015-06-15 19:45:50 -07:00
INSTALL.md Add reference to CircleCi 2015-07-23 21:39:27 -04:00
Makefile.am Include README.md and tests in the release tarball 2015-03-29 18:40:22 +02:00
PERFORMANCE.md Put benchmark results into PERFORMANCE.md 2014-12-08 19:21:33 +01:00
README-NLS remove reference to old autoconf script 2015-06-17 20:47:56 -07:00
README.md add circle to build status 2015-06-19 00:02:44 -07:00
TRANSLATORS Import version 1.4.0 2008-01-07 08:09:04 +00:00

EncFS - an Encrypted Filesystem

Build Status

  • Drone: Build Status
  • Circle: Circle CI

About

EncFS provides an encrypted filesystem in user-space. It runs in userspace, using the FUSE library for the filesystem interface. EncFS is open source software, licensed under the LGPL.

EncFS is now over 10 years old (first release in 2003). It was written because older NFS-based encrypted filesystems such as CFS had not kept pace with Linux development. When FUSE became available, I wrote a CFS replacement for my own use and released the first version to Open Source in 2003.

EncFS encrypts individual files, by translating all requests for the virtual EncFS filesystem into the equivalent encrypted operations on the raw filesystem.

For more info, see:

Status

Over the last 10 years, a number of good alternatives have grown up. Computing power has increased to the point where it is reasonable to encrypt the entire filesystem of personal computers (and even mobile phones!). On Linux, ecryptfs provides a nice dynamically mountable encrypted home directory, and is well integrated in distributions I use, such as Ubuntu.

EncFS has been dormant for a while. I've started cleaning up in order to try and provide a better base for a version 2, but whether EncFS flowers again depends upon community interest. In order to make it easier for anyone to contribute, it is moving a new home on Github. So if you're interested in EncFS, please dive in!

Unique Features

EncFS has a few features still not found anywhere else (as of Dec 2014) that may be interesing to you:

Reverse mode

encfs --reverse provides an encrypted view of an unencrypted folder. This enables encrypted remote backups using standard tools like rsync.

Fast on classical HDDs

EncFS is typically much faster than ecryptfs for stat()-heavy workloads when the backing device is a classical hard disk. This is because ecryptfs has to to read each file header to determine the file size - EncFS does not. This is one additional seek for each stat. See PERFORMANCE.md for detailed benchmarks on HDD, SSD and ramdisk.

Works on top of network filesystems

EncFS works on network file systems (NFS, CIFS...), while ecryptfs is known to still have problems.

Development

The master branch contains the latest stable codebase. This is where bug fixes and improvments should go.

The dev branch contains experimental work, some of which may be back-ported to the master branch when it is stable. The dev branch is not stable, and there is no guarantee of backward compatibility between changes.