search for: p4242

...at indirectly run ssh (like cvs and svn) if they aren't expecting the output. Is this a bug or is there a particular reason enabling debugging on the server is supposed to trigger debug messages on the client? Here's an example connection to a 5.2p1 server started with "sshd -e -D -p4242": $ ssh -p4242 127.0.0.1 'date' Wed Jun 3 11:47:05 PDT 2009 And to a 5.2p1 server started with "sshd -e -ddd -p4242": $ ssh -p4242 127.0.0.1 'date' Environment: USER=... LOGNAME=... HOME=... PATH=... MAIL=... SHELL=......

...Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: petesea at bigfoot.com A server started with debugging options (eg "sshd -e -ddd -p4242") will print debug and "Environment" messages on the client: $ ssh -p4242 127.0.0.1 'date' Environment: USER=... LOGNAME=... HOME=... PATH=... MAIL=... SHELL=... SSH_CLIENT=... SSH_CONNECTION=... debug3: channel 0: close_fds r...