ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00229
Re: [Bug 259631] Re: Cannot open Private directory after a reboot
ubuntostones-
Aha! Thanks for the excellent detective work.
Absolutely, automatic mounting of encrypted ~/Private cannot work with
automatic logins.
Mounting of encrypted ~/Private requires you to enter your password at
login. If you have not done so, the required key is not present, and
thus it will not be mountable.
As I'm a Server Developer (no gui, no automatic logins there), I'll
need to have a discussion with the Desktop guys to collaborate on a
way to solve this.
Thanks,
:-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: 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
References