ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00226
[Bug 259631] Re: Cannot open Private directory after a reboot
Based on above bug descriptions, I figured it might have to do with the
new "automatic login" feature in 8.10. So I clean installed 8.10 final,
enabled "automatic login" through the graphical installer, and followed
the steps required to get the Private directory working. To little
surprise, I can confirm the behaviour:
$ mount.ecryptfs_private
keyctl_search: Required key not available
I tried rebooting, logging out (interestingly enough, logging out with
automatic login logs the user right back in automagically), and many
other voodoo-like things, but I could not get it to work, whether I
removed the folders or used --force.
After disabling automatic login and redoing the steps, it immediately
worked as expected. It auto-mounts now.
I hope that helps.
--
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