From a cryptsetup perspective that's perfectly alright. From a pam_mount
http://bugzilla.novell.com/show_bug.cgi?id=555136#c7 --- Comment #7 from Stefan Tittel <bugreports@tittel.net> 2009-11-17 16:25:51 UTC --- Thanks Ludwig, your packages work fine and fix the "command successful" message to stderr. Any chance we can get it to the update repo? Unfortunately (as Jan already pointed out) this bug is not related to the sudo problem. And indeed, sudo still segfaults. Another little thing I noticed: If a LUKS volume is already mounted and if a second login happens for the same account, pam_mount will say something like: pam_mount(mount.c:67): Errors from underlying mount program: pam_mount(mount.c:71): Command failed: Device _dev_sda8 already exists. pam_mount(pam_mount.c:543): mount of /dev/disk/by-id ata-SAMSUNG_HD501LJ_S0MUJ13P727486-part8 failed perspective it would be much nicer if pam_mount could first check if the volume is already decrypted/mounted before invoking cryptsetup to do it again. At the moment an error will be thrown, even though the system is in a state which the user would not consider to be erroneous (the volume after all is decrypted/mouted). Or did I overlook some option in the man page of pam_mount.conf? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.