Package: ecryptfs-utils Version: 111-2 Severity: normal Dear Maintainer,
0) Use ecryptfs-setup-private to setup a Private directory in a user account. 1) After a fresh boot, if the first login to that user account is via ssh instead of via GUI (lightdm), then the Private dir is not mounted; /dev/shm/ecryptfs-$USER-private exists but is EMPTY (or, if this is your second go-around, contains 0). While still logged via ssh, if you login via GUI, the Private dir is mounted and /dev/shm/ecryptfs-$USER-private contains 1 (which is wrong of course, it should be 2). While still logged in the GUI, if you log out of the ssh session, /dev/shm/ecryptfs-$USER-private becomes 0 and Private is umounted. 2) If the first login is via GUI, Private is mounted and /dev/shm/ecryptfs -$USER-private contains 1. Further logins via ssh do increment it properly, and logouts decrement it properly. Logging out of the GUI with no active ssh session brings you back to condition 1) above. This bug exists in fresh Jessie 8.6 installs as well as in Stretch. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.7.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ecryptfs-utils depends on: ii gettext-base 0.19.8.1-1 ii keyutils 1.5.9-9 ii libassuan0 2.4.3-1 ii libc6 2.24-3 ii libecryptfs1 111-2 ii libgpg-error0 1.24-1 ii libgpgme11 1.7.0-1 ii libkeyutils1 1.5.9-9 ii libpam-runtime 1.1.8-3.3 ii libpam0g 1.1.8-3.3 ii libtspi1 0.3.13-4+b1 ecryptfs-utils recommends no packages. Versions of packages ecryptfs-utils suggests: ii cryptsetup 2:1.7.2-4 -- no debconf information
