← Back to team overview

ecryptfs team mailing list archive

[Bug 259631] Re: Can open Private directory after a reboot

 

Dustin,

ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase [LOGIN_PASSPHRASE] (with my actual login password) returns
Unable to read salt value from user's .ecryptfsrc file; using default fa0ec2d..........

Clicking the link in ~/Private after this does not mount the directory,
and the commands "mount.ecryptfs_private" and "ecryptfs-mount-private"
still gives the error message "keyctl_search: Required key not
available".

ls -la ~/.ecryptfs shows:
drwx------  2 rune rune 4096 2008-10-14 14:26 .
drwxr-xr-x 70 rune rune 4096 2008-10-20 08:51 ..
-rw-r--r--  1 rune rune    0 2008-10-14 14:26 auto-mount
-rw-r--r--  1 rune rune    0 2008-10-14 14:26 auto-umount
-rw-r--r--  1 rune rune   17 2008-10-14 14:26 Private.sig
-r--------  1 rune rune   48 2008-10-14 14:26 wrapped-passphrase


Rune

-- 
Can open Private directory after a reboot
https://bugs.launchpad.net/bugs/259631
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: Invalid

Bug description:
Binary package hint: ecryptfs-utils

I created an encrypted private directory following the instructions here:

https://wiki.ubuntu.com/EncryptedPrivateDirectory

Everything worked as it should until I rebooted. When I try to mount my private directory I get the following message:

 jimk@intrepid:~$ mount.ecryptfs_private
keyctl_search: Required key not available

When I go to create a key, I get the following message:

jimk@intrepid:~$ ecryptfs-setup-private
ERROR: wrapped-passphrase file already exists, use --force to overwrite.

I can create a new passphrase if I use the force option, but I shouldn't have to do this everytime I reboot