ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00053
[Bug 259631] Re: Can open Private directory after a reboot
Same problem here, even after deleting .ecryptfs .Private and Private folders.
After reboot, Private is not automounted.
Doubleclicking on that long softlink found in Private doesnt do anything.
Executing mount.ecryptfs_private in terminal returns: required key not found.
Executing "ecryptfs-mount-private" in terminal does the job, finally.
--
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