Filesystem in userspace (FUSE) with transparent authenticated encryption
securefsis a filesystem in userspace (FUSE) with transparent encryption (when writing) and decryption (when reading).
securefsmounts a regular directory onto a mount point. The mount point appears as a regular filesystem, where one can read/write/create files, directories and symbolic links. The underlying directory will be automatically updated to contain the encrypted and authenticated contents.
From sensitive financial records to personal diaries and collection of guilty pleasures, we all have something to keep private from prying eyes. Especially when we store our files in the cloud, the company and the NSA may well get their hands upon it. The best protection we can afford ourselves is cryptography, the discipline developed by mathematicians and military originally to keep the national secrets.
Security, however, is often at odds with convenience, and people easily grow tired of the hassle and revert to no protection at all. Consider the case of protecting our files either locally or in the cloud: we have to encrypt the files before committing to the cloud and decrypt it every time we need to read and write. Worse still, such actions leave unencrypted traces on our hard drive. If we store data in the cloud, another issue arise: manual encryption and decryption prevent files from being synced efficiently.
securefsis intended to make the experience as smooth as possible so that the security and convenience do not conflict. After mounting the virtual filesystem, everything just works™.
There are already many encrypting filesystem in widespread use. Some notable ones are TrueCrypt, FileVault, BitLocker, eCryptFS, encfs and gocryptfs.
securefsdiffers from them in that it is the only one with all of the following features:
brew install securefs
Linux users have to build it from source.
fusemust be installed.
sudo apt-get install fuse libfuse-dev build-essential cmake.
sudo yum install fuse fuse-devel.
Then clone the sources by
git clone --recursive, and execute
Install using packages (recommended):
bash pkg install fusefs-securefs
bash make -C /usr/ports/sysutils/fusefs-securefs install
Make sure you load the fuse kernel module before using securefs:
bash kldload fuse sysrc -f /boot/loader.conf fuse_load="YES" # Load fuse automatically at boot
It is recommended to disable or encrypt the swap and hibernation file. Otherwise plaintext and keys stored in the main memory may be written to disk by the OS at any time.
securefs --help securefs create ~/Secret securefs chpass ~/Secret securefs mount ~/Secret ~/Mount # press Ctrl-C to unmount securefs m -h # m is an alias for mount, -h tell you all the flags
There are two categories of filesystem format.
The lite format simply encrypts filenames and file contents separately, similar to how
encfsoperates, although with more security.
The full format maps files, directory and symlinks in the virtual filesystem all to regular files in the underlying filesystem. The directory structure is flattened and recorded as B-trees in files.
The lite format has become the default on Unix-like operating systems as it is much faster and features easier conflict resolution, especially when used with DropBox, Google Drive, etc. The full format, however, leaks fewer information about the filesystem hierarchy, runs relatively independent of the features of the underlying filesystem, and is in general more secure.
To request full format, which is no longer the default, run
securefs create --format 2.
If you store
securefsencrypted files on iCloud Drive, it might cause Spotlight Search on iOS to stop working. It is a bug in iOS, not in
To work around that bug, you can disable the indexing of Files app in Settings -> Siri & Suggestions.