Ah, a little more information - this segv only happens when using password authentication (ssh keys work fine)
sshd_config has UsePAM yes PubkeyAuthentication yes PasswordAuthentication yes ChallengeResponseAuthentication no Richard Nelson wrote: > # /usr/sbin/sshd -Dddd >~/log 2>&1 > Segmentation fault > > The last lines of log: > debug3: mm_auth_password entering > debug3: mm_request_send entering: type 11 > debug3: mm_auth_password: waiting for MONITOR_ANS_AUTHPASSWORD > debug3: mm_request_receive_expect entering: type 12 > debug3: mm_request_receive entering > debug3: monitor_read: checking request 11 > debug1: do_cleanup > debug1: PAM: cleanup > debug3: PAM: sshpam_thread_cleanup entering > > gdb isn't very helpful > Program received signal SIGSEGV, Segmentation fault. > 0x00002acda6fe7af2 in ?? () > (gdb) bt > #0 0x00002acda6fe7af2 in ?? () > #1 0x00002acda692ad86 in ?? () > #2 0x0000000000000050 in ?? () > #3 0x0000000000000001 in ?? () > #4 0x00007fff05c7cf10 in ?? () > #5 0x0000000000000000 in ?? () > (gdb) quit > The program is running. Exit anyway? (y or n) y > debug1: do_cleanup > debug1: PAM: cleanup > debug3: PAM: sshpam_thread_cleanup entering > > I installed libpam-dbg, but still didn't get any information > > removing pam_krb5 from /etc/pam.d/common-auth fixes the problem > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
