I did a quick gdb run on the system that Paul mentions. I first ran "ssh user@localhost" and then I ran gdb on the first of the two "sshd: unknown [priv]" processes (which is the one that crashes). After gdb was attached I entered a random password (the test account in question didn't exist so no password would get a login).
At the point of the crash gdb said: Program received signal SIGTRAP, Trace/breakpoint trap. 0x000000000044e1b5 in ?? () After that I could use the "c" command in gdb to keep running and my ssh client would ask me for another password (the expected action). When I did the same thing without gdb the sshd process would SEGV. It seems that there is some debugging code enabled in ssh or it's libraries. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
