Package Details: ecryptfs-simple 2016.12-1

Git Clone URL: (read-only)
Package Base: ecryptfs-simple
Description: A very simple utility for working with eCryptfs.
Upstream URL:
Keywords: encryption
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 14
Popularity: 0.836098
First Submitted: 2012-05-29 20:03
Last Updated: 2016-12-03 18:46

Latest Comments

Xyne commented on 2016-12-23 14:03

Thanks for posting an explanation. Sorry to everyone who was affected by the silent truncation bug.

mobad commented on 2016-12-22 17:44

For the people who are having problems decrypting with the latest version, it's likely due to the older versions of ecryptfs-simple silently truncating your password to 15 characters.

I tried everything to get it to mount but the fix in the end was to just use the first 15 characters of my password.

I really recommend people that were using ecryptfs-simple to create a new ecryptfs mount and copy everything to it.

Xyne commented on 2016-11-16 05:03

It should work again.

For anyone curious about the recent activity after years of no updates, it has been prompted by a discussion on the forum:

marcarch commented on 2016-11-15 08:39


I've got an issue with the version 2016.11.15.1.
When entering the passphrase as prompted, the decryption failes.

> ecryptfs-simple -o key=passphrase -a <dir1> <dir2>
> Mounting <dir1> on <dir2>
> Passphrase: error: option prompt failed

The downgrade to ecryptfs-simple 2016.11 solved the problem.

Distag commented on 2016-11-14 10:50

Hello, there is a problem with this new update. I cannot decrypt my files.

I take back the ecryptfs-simple-2016.11.13.tar.xz and I can read back my files with it.

Xyne commented on 2015-01-15 05:31

I have updated the upstream signature.

hschletz commented on 2015-01-14 17:31

PKGBUILD forces new signing key (8F173680), but package is still signed with the old key (C2E5C0D2). Had to edit PKGBUILD to use the old key to proceed.

Xyne commented on 2013-09-24 20:05

I have encounted problems with eCryptFS (independent of ecryptfs-simple) that have led to data loss. I can no longer recommend the use of eCryptFS. I will continue to maintain this package, but I strongly suggest that users switch to something else such as encfs.

If there are any ecryptfs enthusiasts who know how to recover from random input/output errors, please let me know and I may reconsider this stance.