Package Details: ecryptfs-simple 2017-2

Git Clone URL: (read-only, click to copy)
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: 20
Popularity: 0.026147
First Submitted: 2012-05-29 20:03
Last Updated: 2017-07-04 11:02

Latest Comments

1 2 3 Next › Last »

gash commented on 2020-02-22 05:32

Any passphrase is ok for mounting. When I 'ecryptfs-simple /low /upper' second and other times, I can provide any passphrase differ from passphrase I provided first time - mount is ok and I can see mounted catalog content.

petaramesh commented on 2020-02-16 09:53

Could you please add the architecture "aarch64" (ARM 64, double a intended) in the PKGBUILD file ? It will allow it to compile and run nicely on a RaspberryPi 4 :) (Tested working)

mwohah commented on 2017-07-06 17:37

In case anyone's still wondering: it seems to be solved with systemd 233.75-2.

Xyne commented on 2017-07-05 11:56

If it's a systemd/ecryptfs-utils issue then we'll just have to wait until that's solved. If the problem persists after that then I will try to fix it.

hschletz commented on 2017-07-04 18:00

Looks like systemd 233 broke some ecryptfs tools:

I can still mount manually ("sudo mount -t ecryptfs ...") using the options from the config file ("ecryptfs-simple --print-config-path /home/foo/.Private").

mwohah commented on 2017-07-04 17:31

Since installing the latest updates on 2017-07-03 (lvm2 2.02.172-1, systemd 233-6, device-mapper 2.02.172-1, ...), ecryptfs-simple completely seems to have broken for me.

The CLI lists the following output after entering the (correct) passphrase:

> error: mount failed
> No such file or directory

The journal lists the following issues:

> Error parsing options; rc = [-2]
> One or more global auth toks could not properly register; rc = [-2]
> Could not find valid key in user session keyring for sig specified in mount
> process_request_key_err: No key
> Could not find key with description: [XXXXXXXXXXXXXXXX]

This happens with both ecryptfs-simple 2017-2 as well as the one from 2016.12-1 (I hadn't updated my AUR packages yet when I updated Arch, but I have now).

I'm experiencing no problems with ecryptfs via GDM and my encrypted home partition, however, which is strange.

To verify that I wasn't just typing the wrong password over and over and was somehow confused, I tried creating a completely new ecryptfs folder, which gives me the same error. I don't seem to be able to do anything with the utility anymore.

May be related to recent Arch package updates, seeing as I've been using it without problems every day before doing the Arch updates on 3 July.

Not sure if this is a bug or something else is going on and wasn't sure where to report this. Apologies if it's in the wrong place.

Xyne commented on 2017-07-04 11:29

fixed with 2017-2

hschletz commented on 2017-07-03 18:26

The source URL gives a 404 for the latest version.

Xyne commented on 2017-07-03 09:22

I'll try to fix this as soon as I have some time (hopefully later today).

edit: It should be fixed with ecryptfs-simple-2017

esilva commented on 2017-06-28 14:47

Scanning dependencies of target ecryptfs-simple
[ 50%] Building C object CMakeFiles/ecryptfs-simple.dir/src/ecryptfs-simple.c.o
[100%] Linking C executable ecryptfs-simple
CMakeFiles/ecryptfs-simple.dir/src/ecryptfs-simple.c.o: In function `main':
ecryptfs-simple.c:(.text.startup+0x21c): undefined reference to `copy_string_n'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/ecryptfs-simple.dir/build.make:97: ecryptfs-simple] Error 1
make[1]: *** [CMakeFiles/Makefile2:100: CMakeFiles/ecryptfs-simple.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().