ecryptfs team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

I activated auto-login, rebooted, and as expected ended up with
~/Private being unmounted. It had one file in it:

  lrwxrwxrwx 1 martin martin 28 2008-10-28 16:54 THIS DIRECTORY HAS BEEN
UNMOUNTED TO PROTECT YOUR DATA --  Run mount.ecryptfs_private to mount
again -> /sbin/mount.ecryptfs_private

There was no "readme.txt" file as I would have expected from the
debdiff. Also, running this script (or mount.ecryptfs_private directly)
did not work, I wasn't prompted for my password and the process just
exited with status 1. The only way to recover was to open a terminal and
do "su - martin".

So this doesn't work for me.

-- 
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: Fix Committed
Status in ecryptfs-utils in Ubuntu Intrepid: Fix Committed

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