Am 06.05.2010 20:38, schrieb Stefan G. Weichinger: > The main question is still unanswered: Why does pam_mount not work > anymore with the given device/key ?
additional digging: I found http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528366 where the poster tries the underlying mount.crypt call. I did that as well and get: # mount.crypt -v -o fsk_cipher=aes-256-cbc,fsk_hash=md5,keyfile=/etc/security/verysekrit.key /dev/VG01/crypthome /mnt/gschwind command: 'readlink' '-fn' '/dev/VG01/crypthome' command: 'readlink' '-fn' '/mnt/gschwind' Password: mount.crypt(crypto-dmc.c:144): Using _dev_dm_0 as dmdevice name crypt_activate_by_passphrase: Operation not permitted which is in fact the error pam_mount throws up : pam_mount(mount.c:64): Errors from underlying mount program: pam_mount(mount.c:68): crypt_activate_by_passphrase: Operation not permitted Downgrade pam_mount from 2.1 to 2.0 ... same error. But it works with pam_mount 1.33 ! I don't know which old bugs I reintroduce to my system by doing this ;-) I think I am gonna file a bug for this now. Stefan
