← Back to team overview

ecryptfs team mailing list archive

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

 

Dustin, here's the output of the grep command:
/etc/pam.d/common-auth:auth	optional	pam_ecryptfs.so unwrap
/etc/pam.d/common-password:password	optional	pam_ecryptfs.so 
/etc/pam.d/common-session:session	optional	pam_ecryptfs.so unwrap

I'm still at the point where it will work after a reboot, but not
immediately, I have to wait at least 5 minutes now before it will mount.
I don't need it to automount though...

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



Follow ups