← Back to team overview

ecryptfs team mailing list archive

[Bug 259631] Re: Cannot open Private directory after a reboot when "Automatic Login" enabled

 

I'm attaching a debdiff that fixes this for Intrepid, and request that
this be sponsored for intrepid-proposed.  I'll do the SRU momentarily.

:-Dustin

** Also affects: ecryptfs
   Importance: Undecided
       Status: New

** Changed in: ecryptfs
   Importance: Undecided => Medium
     Assignee: (unassigned) => Dustin Kirkland (kirkland)
       Status: New => In Progress

** Changed in: ecryptfs-utils (Ubuntu)
   Importance: Undecided => Medium
       Status: Confirmed => In Progress

** Attachment added: "ecryptfs-utils.259631.debdiff"
   http://launchpadlibrarian.net/19315281/ecryptfs-utils.259631.debdiff

-- 
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: In Progress
Status in “ecryptfs-utils” source package in Ubuntu: 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