Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-24 Thread Bastian Kleineidam
Am Tuesday 24 February 2009 18:45:30 schrieb Wearenotalone: > Anymore questions? Not at the moment. Your information should be enough to reproduce the problem, which I will try to do in the next days. Thanks, Bastian signature.asc Description: This is a digitally signed message part.

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-24 Thread Wearenotalone
Hello, Bastian Kleineidam schrieb: Hi, Am Friday 20 February 2009 11:50:48 schrieb Wearenotalone: Yesterday i continued looking for a solution to my problem. At first i changed my definition to Was there a mount error without the changes? The options fsk_cipher and fsk_hash are dup

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-24 Thread Bastian Kleineidam
Hi, Am Friday 20 February 2009 11:50:48 schrieb Wearenotalone: > Yesterday i continued looking for a solution to my problem. At first i > changed my definition to > > options="fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,f >sck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essi

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-20 Thread Wearenotalone
The first solution seems to be incomplete. If the keybits option is given then the loop device (/dev/loop1) on top of the LUKS partition is not created (correct behavior), BUT the loop device of the /my/encrypted.img file (/dev/loop0) is not removed after luksClosing /dev/mapper/_my_encrypted_i

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-20 Thread Wearenotalone
I think i have identified the cause of my unmount problem. The mount option keybits implies the loop option. This causes the LUKS partition again to be mounted as a loop device. At the moment mount.crypt only filters the loop option but not the keybits option. Usualy this is no problem because

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-20 Thread Wearenotalone
Yesterday i continued looking for a solution to my problem. At first i changed my definition to options="fsk_cipher=aes-256-cbc,fsk_hash=sha512,keyfile=/my/encrypted.key,fsck,noexec,nodev,nosuid,relatime,cipher=aes-cbc-essiv:sha256,keybits=256,hash=sha512" fskeypath="/my/encrypted.key" user="M

Bug#516003: segfault caused by umount.crypt after libpam-mount update

2009-02-18 Thread WANA
Package: libpam-mount Version: 1.9-1 Severity: important After upgrading libpam-mount from the latest Debian Lenny version (0.44-1+lenny3) to the latest Squeeze version (1.9-1) i get a segfault from umount.crypt everytime i logout. The encrypted directory is successfully unmounted, but i get t