https://bugzilla.mindrot.org/show_bug.cgi?id=2355
Darren Tucker <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from Darren Tucker <[email protected]> --- (In reply to Christoph Anton Mitterer from comment #6) > (In reply to Damien Miller from comment #2) > > Could you try running a sshd in debugging mode on a different port > > (i.e. "sshd -dddp 2222") and catching it in the act of crashing? > > Seeing where it fails would be a great help. > Sure, see attached files: sshd and ssh output, from the later you > see which tries failed (with which error) and which worked. > > Interestingly, the sshd quite *every time* after the end of the > connection... is this because of -D? -D and -d mean different things, but yes -d means "run in debug mode once then exit". If you want to leave it up you can use this instead of -d: /path/to/sshd -De -o LogLevel=debug3 > (In reply to Damien Miller from comment #3) > > BTW, I can't replicate this with HEAD > Mhh and have you tried with an older tag as well (i.e. 6.7p1?) and > could replicate it there? Note that you are running a vendor-modified version of OpenSSH: Local version string SSH-2.0-OpenSSH_6.7p1 Debian-3 It's not all that easy for us to know exactly what each vendor has changed. Even things like which compiler flags they use can make a difference. Have you reported this to Debian? They're in a much better position to reproduce a problem. -- You are receiving this mail because: You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
