Hello again! I've got another twist on this bug! Last night, I tried logging into a machine that is showing this problem. I was logging in using SSH, using the PuTTY Windows SSH client. At the time I made the connection, I entered the wrong username by mistake, but I did not catch my mistake until I had finished entering my password. After entering the password, PuTTY just sat for a while, waiting, and then reported that the remote side had closed the connection.
Once I got back into work, I did a test with this on my workstation (also running Ubuntu Hardy, fully up-to-date), and I discovered the following: If you have PAM configured to use Heimdal's pam_krb5.so module, and you try to log in with an invalid username, openssh-server's sshd will crash in the same place as dovecot-imapd. Since I did the verification on my Linux workstation, I had apport running, and it grabbed a crash report. I processed the crash report with `appport-cli -c` and saved the report, so it has the core dump AND all of the information that is derived from the core dump. I really hope this extra info helps! ** Attachment added: "usr_sbin_sshd.0.crash" http://launchpadlibrarian.net/35196951/usr_sbin_sshd.0.crash -- Dovecot-imapd, PAM auth., krb auth with non-krb user causes crash https://bugs.launchpad.net/bugs/414359 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
