← Back to team overview

ecryptfs team mailing list archive

[Bug 256154] Re: pam_ecryptfs should respect ~/.ecryptfs/auto-[u]mount files

 

Dustin, thanks again. There have never been any settings in my ~/Private, I just copied some data there to test it. Now I emptied it completely, but logging in to Xfce is still impossible when I delete the two auto-[u]mount files.
Code: 
~/Private$ ls -a
.  ..
when it is mounted - which means there is really no data at all, am I right?

To be more precise: There was an old backup of a home folder from Jaunty
Beta, named home_beta or so; I copied that to Private. But I never
pointed any software there. Now I've moved it away. Maybe there was a
problem with links inside the old home folder? I removed one to the
general examples folder, but that did not change anything.

-- 
pam_ecryptfs should respect ~/.ecryptfs/auto-[u]mount files
https://bugs.launchpad.net/bugs/256154
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” source package in Ubuntu: Fix Released

Bug description:
Binary package hint: ecryptfs-utils

>From user feedback on the https://wiki.ubuntu.com/EncryptedPrivateDirectory wiki page...

 * "I hope there will also be an option for the ~/Private directory to ''not'' be mounted at login"

Additionally, it would be nice to allow a user to "not unmount" ~/Private automatically on logout.

The hooks are already in place in ecryptfs-setup-private to create the ~/.ecryptfs/auto-mount and ~/.ecryptfs/auto-umount files.  We simply need to teach pam_ecryptfs to respect that configuration.

:-Dustin