saslauthd segfaults with pam_krb5
Hi
Not sure if this should be to sent to debian-user or debian-testing
I am trying to use saslauthd -a pam to authenicate a cyrus 2.2.5 server
against a MIT kerberos.
If I enter the wrong password for a user the login fails and saslauthd
stays running.
If I enter the correct password for kerberos I get
auth.log
Jun 18 11:02:42 mail2 saslauthd[3558]: pam_krb5:
pam_sm_authenticate(imap csad): entry:
Jun 18 11:02:42 mail2 imap[3561]: size read failed
saslauthd -a pam -n 1 -d output
saslauthd[3558] :main : num_procs : 1
saslauthd[3558] :main : mech_option: NULL
saslauthd[3558] :main : run_path : /var/run/saslauthd
saslauthd[3558] :main : auth_mech : pam
saslauthd[3558] :ipc_init : using accept lock file:
/var/run/saslauthd/mux.accept
saslauthd[3558] :detach_tty : master pid is: 0
saslauthd[3558] :ipc_init : listening on socket:
/var/run/saslauthd/mux
saslauthd[3558] :main : using process model
saslauthd[3558] :get_accept_lock : acquired accept lock
saslauthd[3558] :rel_accept_lock : released accept lock
saslauthd[3558] :do_auth : auth failure: [user=root]
[service=imap] [realm=] [mech=pam] [reason=PAM auth error]
saslauthd[3558] :get_accept_lock : acquired accept lock
saslauthd[3558] :rel_accept_lock : released accept lock
Segmentation fault
If I remove pam_krb5 from stack and use user in password file pam_unix
authenticates me fine
Any ideas where to look
present test imap pam file is
auth sufficient pam_krb5.so debug
auth sufficient pam_unix.so debug
auth required pam_deny.so
account sufficient pam_permit.so
Cheers
Matt
Reply to: