Comment 15 for bug 234727

David, thanks for tracking this down. So it seems that there are really two independent issues here: (1) pam_verify() being called with a NULL prompt, triggering the crash; and (2) sudo -u not asking for the user's password in cases where you use libpam_mount? Or did you mean that sudo -u *does* ask for the password, but in vain, since it immediately closes the PAM session again (which would then be the real bug)?

BTW, using sudo in init scripts is not common practice or recommended at all. They should use su, and only to system users, which should not ever have an encrypted home directory. So I don't think that this bit is a problem.

Thanks for clarification! Once this is settled, this should be forwarded upstream (first the crash, which is easy enough, and then also your followup problem).