← Back to team overview

ecryptfs team mailing list archive

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

 

Dustin,

thanks a lot for working on this. I read the upstream commit, and it is
a great improvement to the current situation. Using a Terminal is okay
for now, since there are no cross-distro tools for DE agnostic password
input. Using gksu if it exists would be a nice improvement, of course. I
really like the idea of using a .desktop file, that should behave very
well in file managers.

As for your debdiff:

  * Please don't use /usr/share/app-install/ for the .desktop file.
That's used by gnome-app-install, and announcing this as an application
doesn't make sense. For the same reason it shouldn't be under
/usr/share/applications. I suggest to simply use /usr/share/ecryptfs-
utils/.

 * Minor gotcha: You install ecryptfs-mount-private.txt into
/usr/share/doc/ecryptfs-utils/. Debian Policy (12.3) requires that you
are able to rm -r /usr/share/doc without any program behaviour. Also, it
is not really helpful documentation in the sense of "I read this before
installation". Thus I suggest to put it into /usr/share/ecryptfs-utils/,
too.

 * debian/ecryptfs-utils.install: Oh, I wasn't aware that it's possible
nowadays to specify absolute paths. If that works, I learned something
new today. :-)

Many thanks for working on this!

-- 
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

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