http://bugzilla.novell.com/show_bug.cgi?id=555136 Summary: cryptsetup prints "command successful" message to stderr breaking pam_mount and possibly sudo Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bugreports@tittel.net QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 The cryptsetup version shipped with openSUSE 11.2 prints "Command successful." to stderr, if the command succeeded. If pam_mount is used to transparently decrypt a LUKS volume (using cryptsetup), pam_mount will complain after login with: pam_mount(mount.c:67): Errors from underlying mount program: pam_mount(mount.c:71): Command successful. Unfortunately this can easily result in programs dealing with PAM/user authentication believing that the process was not successful (even though it was). Most notably when pam_mount is activated, sudo will just give this (no matter if tried as root or tittel and no matter which command is used): tittel@earth:~$ sudo ls root's password: Segmentation fault I believe it is most likely that the stderr problem of cryptsetup is causing sudo to segfault. In bug 544154 another user reported something similiar. However it is theoretically possible that it is problem between pam_mount and sudo unrelated to the stderr issue of cryptsetup. There seems to be a patch to make cryptsetup behave: http://code.google.com/p/cryptsetup/issues/detail?id=35 Also the maintainer of pam_mount seems to be aware of the issue: http://sourceforge.net/tracker/index.php?func=detail&aid=2834188&group_id=41452&atid=430593 I would be happy to help narrowing down this problem, because whilst getting wrong error messasage on login is just a bit annoying, the total lack of a working sudo is a dealbreaker for me at the moment. Thanks in advance! Reproducible: Always -- 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.