"Livingston, John A" <john.a.livings...@boeing.com> writes: > On Jun 4, 2012, at 6:10 PM, Russ Allbery wrote:
>> Are you using libpam-krb5? If so, could you upgrade to the version >> just uploaded to unstable? The version in testing will segfault if >> krb5_init_context fails; the version in unstable will instead try to >> give you some sort of error message. > Just updated to 4.6-1 from unstable, it doesn't appear to have had any > effect. I still see a protection fault on password authentication with > no other errors printed, and login with an existing Kerberos ticket is > still working perfectly. Oh well, so much for that theory. Usually, segfaults in sshd are actually in a PAM module, but they can be rather hard to track down. Could you try running sshd on a separate port with the -d flag so that you can get a trace on the server of where the segfault happens? You may be able to capture a core dump that way so that you can get a backtrace and see where it's exploding. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
