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.064590
First Submitted: 2012-05-29 20:03
Last Updated: 2016-12-03 18:46

Latest Comments

nicolasgeniteau commented on 2017-06-01 14:42


Since the last update of gcc, ecryptfs-simple doesn't build anymore :
ecryptfs-simple.c:(.text+0x858): undefined reference to `copy_string_n'

Removing the inlining of the function seem to fix the error.

Xyne commented on 2017-02-27 23:15

I am able to create two empty directories, mount one on the other with ecryptfs-simple, create a file in the mounted directory, and inspect and manipulate both (plaintext & encrypted) via standard tools (ls, cat, rm).

I suspect that there is something else wrong with your system if the file permissions were changed on the entire partition. Check your system logs (syslog, journalctl, dmesg, etc.) for errors and maybe run a test on the disk with smartctl.

Sandi commented on 2017-02-24 15:15

I'm experiencing some weird behavior. I made two directories dir1 and dir2 for testing purposes, with a text file in dir1. Then I ran:

$ sudo modprobe ecryptfs
$ ecryptfs-simple dir1 dir2

After setting the passphrase and all other required settings, dir2 now contains the same text file, which is visible with ls. But, cat complains about input/output something or other when I try to read it, sublime displays an empty file, rm says the file doesn't exists, and sudo rm won't remove it because it's busy.

I ran ps aux | grep ecryptfs to see what's keeping it busy, finding a program called ecryptfs-kthrea (sic). It cannot be killed with -15, -1 or -2, not even by root. Restarting is the only way I've found to get rid of it.

Another weird thing is that both dir1 and dir2 are owned by root even though I created them. In fact, all the files on my data partition have ownership root root all of a sudden. I'm not sure if this was the case before, but I have read/write permission for them and I have created them all.

I should say I'm on Manjaro (but the package is from AUR installed via yaourt), running KDE.

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.

All comments