← Back to team overview

ecryptfs team mailing list archive

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

 

Rune-

Cool, thanks for the details.  Multiple keys in the keyring should be
fine.  The file ~/.ecryptfs/Private.sig tells mount.ecryptfs_private
which key should be used.

It sounds like your PAM configuration isn't correct.

Could you please post /etc/pam.d/common-session, /etc/pam.d/common-auth,
and /etc/pam.d/common-password?

Also, could you indulge me with your ecryptfs and pam versions?
 $ dpkg -l | grep ecryptfs
 $ dpkg -l | grep pam

:-Dustin

-- 
Cannot 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: Incomplete

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