On Mon, 2009-07-20 at 07:32 -0700, Russ Allbery wrote: > Jonathan Guthrie <jguth...@brokersys.com> writes:
> > After updating libpam-krb5 on two different systems, it became impossible > > for non-root users to log in, and attempting to log in results in a message > > like this being printed on this screen: > > [ 4842.563470] login[5519]: segfault at 0 ip b7fa5f1e sp bffda680 error 4 in > > pam_krb5.so[b7fa2000+9000] > > and then I get a new login prompt > Works fine for me, so I need more information. Can you get a backtrace > from the login segfault, for example? Also, please turn on debug in the > PAM configuration and send the syslog output. Thank you for your prompt response. I will do what I can to get you the information that you need. I don't know how to get a backtrace from the login segfault, so I downloaded and built V0.1.2 of pamtester, and it dumps a core file that has this as a backtrace: #0 0xb7f22f1e in ?? () from /lib/security/pam_krb5.so #1 0xb7f21da6 in pam_sm_authenticate () from /lib/security/pam_krb5.so #2 0xb7f123b1 in ?? () from /lib/libpam.so.0 #3 0xb7f11c0d in pam_authenticate () from /lib/libpam.so.0 #4 0x080491ff in pamtester_app_run () #5 0x0804aead in main () If you can tell me how to get a backtrace from login, and would prefer that, I will give you that, too. Since su and sudo also don't work for me with the upgraded, package, adding debug to the line in /etc/pam.d/common-auth and attempting a "sudo ls /", then an ssh in from remote, then an "su jguthrie" puts these items in the log: Jul 20 12:59:16 husky sudo: (pam_krb5): none: pam_sm_authenticate: entry (0x8000) Jul 20 12:59:16 husky sudo: (pam_krb5): jguthrie: attempting authentication as jguth...@brokersys.com Jul 20 12:59:16 husky kernel: [19312.210390] sudo[21912]: segfault at 0 ip b80acf1e sp bfed85f0 error 4 in pam_krb5.so[b80a9000+9000] Jul 20 13:03:19 husky sshd[22039]: (pam_krb5): none: pam_sm_authenticate: entry (0x1) Jul 20 13:03:19 husky sshd[22039]: (pam_krb5): jguthrie: attempting authentication as jguth...@brokersys.com Jul 20 13:03:19 husky kernel: [19556.035532] sshd[22039]: segfault at 0 ip b797bf1e sp bff28150 error 4 in pam_krb5.so[b7978000+9000] Jul 20 13:03:25 husky su[22042]: (pam_krb5): none: pam_sm_authenticate: entry (0x0) Jul 20 13:03:25 husky su[22042]: (pam_krb5): jguthrie: attempting authentication as jguth...@brokersys.com Jul 20 13:03:25 husky kernel: [19561.464285] su[22042]: segfault at 0 ip b7c8ef1e sp bfc38e20 error 4 in pam_krb5.so[b7c8b000+9000] I CAN run kinit and successfully get a key. I can only test with pamtester and sshd until this evening as I'm doing all this remotely from work, so I don't have access to the console until 8 or so (Houston time) tonight. > There weren't many changes between 3.13 and 3.14, so I'm rather confused > by this. I can't think of what changed that could be causing these > symptoms. If you'd like, I can try building it from source and trying to debug it that way. It might be easier than having you tell me what data to gather. Let me know what you'd prefer. !DSPAM:77,4a64b256125333244113768! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
