Bug#425314: $HOME still in use after session has been closed - Steps to reproduce

[Christian Kastner <techmail@kvr.at>]

I installed etch on a spare partition of another computer, and I have
the problem there as well. Below you will find the steps to reproduce
the problem.

1) Install Debian etch. Select only "Standard" in the tasksel dialog.

2) After reboot, install the following packages / meta-packages:
    * xserver-xorg
    * kde
    * cryptsetup
    * libpam-mount

3) As root, create a dm-crypt device with cryptsetup (the password
   should be identical to the login password):

root@sandbox # cryptsetup -c aes-cbc-essiv:sha256 -h sha512 foohome /dev/hda8
-> /dev/mapper/foohome created

4) Create a filesystem on it (I chose JFS)

5) Mount the filesystem somewhere, and move the contents of a
   user's home directory to it.

6) Add an appropriate entry to /etc/security/pam_mount.conf.
   This example here corresponds to the cryptetup params above:

# volume <user> <type> <server> <volume> <mount point> <mount options> <fs key cipher> <fs key path>
volume foobar crypt - /dev/hda8 /home/foobar fsck,noexec,nosuid,nodev,fstype=jfs,cipher=aes-cbc-essiv:sha256,hash512 - -

7) Finally, added the following line to the end of /etc/pam.d/kdm:
@include common-pammount


If you now login and logout again, umount and removal of the
encrypted device will fail. Enabling debug mode in
/etc/security/pam_mount.conf will show three kdeinit
processes keeping $HOME and $HOME/.xsession-errors open.

Regards,
Christian


-- 
Christian Kastner
PGP Key: AE90E13F