ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #00246
[Bug 259631] Re: Cannot open Private directory after a reboot when "Automatic Login" enabled
Thanks! I fixed the upload target to "intrepid-proposed" and uploaded.
I'll accept it once the previous SRU (bug #290445) is verified and moves
to -updates.
** Changed in: ecryptfs-utils (Ubuntu Intrepid)
Status: New => In Progress
--
Cannot open Private directory after a reboot when "Automatic Login" enabled
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 - Enterprise Cryptographic Filesystem: Fix Committed
Status in “ecryptfs-utils” source package in Ubuntu: In Progress
Status in ecryptfs-utils in Ubuntu Intrepid: In Progress
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