[Bug 1719] Debug server prints debug messages on client

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=1719

--- Comment #2 from petesea at bigfoot.com 2010-04-10 03:13:42 EST ---
(In reply to comment #1)
> You can prevent (most of this) by specifying -e to sshd, eg:
> 
> /usr/local/sbin/sshd -De -o loglevel=debug3 -p 2022

This is true, BUT -D is not the same thing as -d.   The reason I'm
using -d is so the server only runs one time and then exits.  This
doesn't happen with -D.   And as you point out, even with -D
-ologlevel=debug3, there is still a debug3 message generated on the
client.

Running -d or -dd will generate the "Environment" message on the
client, which is actually more troublesome then the "debug" message
generated with -ddd, because it's not an obvious debug message.

I'd be happy to supply a patch for this, but I'm at a loss as to why
the "Environment" and errant "debug3" messages are generated on the
client.  How does setting debug on the server trigger debug on the
client, but only for some messages?   Does it have to do with when the
message is printed with regards to the creation of the tunnel?

The "Environment" message appears to be coming from session.c line 1299
(as of CVS 2010-04-09).  That code is wrapped with "if (debug_flag)". 
The "debug3" message appears to come from channels.c line 375.  How is
checking the debug_flag and/or calling the debug3() function different
at those points then another other point in the code?

-- 
Configure bugmail: https://bugzilla.mindrot.org/userprefs.cgi?tab=email
------- 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.