https://bugzilla.novell.com/show_bug.cgi?id=461333
User e.kunig@home.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=461333#c22
--- Comment #22 from Egbert König
pam_mount before 1.0 always used md5 for fsk_hash. You need ot use that instead of sha1 then.
mount.crypt -v -ofsk_cipher=aes-256-cbc,fsk_hash=md5,keyfile=/home/egbert.key /home/egbert.img /home/egbert works. Here is the output: command: [readlink] [-fn] [/home/egbert.img] command: [readlink] [-fn] [/home/egbert] Password: mount.crypt(loop.c:124): Setting up loop device for file /home/egbert. img mount.crypt(loop.c:135): Using /dev/loop0 mount.crypt(crypto-dmc.c:137): Using _home_egbert_img as dmdevice name command: [cryptsetup] [luksOpen] [/dev/loop0] [_home_egbert_img] Command successful. key slot 0 unlocked. command: [mount] [-n] [/dev/mapper/_home_egbert_img] [/home/egbert] umount.crypt -v /home/egbert does not work. Here is the output: Command failed. umount.crypt(crypto-dmc.c:160): Could not unload dm-crypt device "/dev/mapper/_home_egbert_img", cryptsetup returned HXproc status 237 I will provide strace output in an attachment. pam_mount still does not work. I will attach debug messages from /var/log/messages and pam_mount.xml. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.