ecryptfs team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Beleriand [2008-11-27  9:01 -0000]:
> That's what I thought, too. And for that reason I think it's a feature
> not to mount the encrypted directory on login and not a bug.

It *can't* be a bug. If it would be possible to unlock the encrypted
directory fully automatically, then you don't need to encrypt it in
the first place. It would not bring *any* security in that case.

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