Bug#765854: ecryptfs-utils: Private directory not automatically unmounted anymore on logout

[László Böszörményi (GCS)]

On Sun, Jan 8, 2017 at 10:04 PM, Julian Andres Klode <jak at debian.org> wrote:
> On Sun, Jan 08, 2017 at 09:32:25PM +0100, Martin Pitt wrote:
>>  so the mount/unmount needs to be done by a PAM module
>> (pam_ecryptfs). This works just fine in Ubuntu at least (I've used ecryptfs on
>> my $HOME for many years).
 Yes, PAM should handle this. Question is, does it work reliably?
Please read on.

> Really? That said, Ubuntu switched with 15.04, and I reported the bug
> in 14. But then László can reproduce it now it seems, so I don't think
> that's really fixed anywhere.
>
> Then it's really a question of why this happens in Debian (and others[1][2])
> and not in Ubuntu. Or debugging the pam module.
 I've created several users to test -4 with the systemd service file
you provided under /usr/lib/systemd/user/ and it works for some users
and not for others. What I've found, it depends on
~/.ecryptfs/auto-mount . If it doesn't exists, then the user has to
mount ~/Private with ecryptfs-mount-private of course. But then if
s/he logouts, ~/Private is unmounted automatically (PAM or systemd
file, not tested). If you just touch ~/.ecryptfs/auto-mount and logout
- login, then ~/Private is auto mounted and _not_ unmounted on logout.
Then you login again, remove ~/.ecryptfs/auto-mount and logout with
~/Private unmounted automatically this time.

Please test it vica-versa on systems the unmount works / not works - I
think you will find the same dependency on working.

Laszlo/GCS