search for: ssh_msg_debug

...sn't an OpenSSH bug, but just in case anyone else is ambitious enough to automatically run interoperability tests against other SSH implementations, here's a heads-up: https://twistedmatrix.com/trac/ticket/9422 TL;DR: commit 7c856857607112a3dfe6414696bf4c7ab7fb0cb3 caused there to be an SSH_MSG_DEBUG message sent where there wasn't one before, which tripped over an implementation bug in Twisted. I'm guessing slightly at the affected version range based on git history. -- Colin Watson [cjwatson at debian.org]

...havior comes from. This behavior can be seen here: --snip-- $ ssh u at u 2>&1 | sed -n l ssh: Could not resolve hostname u: Name or service not known\r$ --snip-- I have seen section 11.3 from rfc4253, but am unsure whether that is the origin of this behavior. Is a "Debug Message"(SSH_MSG_DEBUG) considered anything that is logged on stderr? Any insights welcome! Cheers, Josh

...; > enough to automatically run interoperability tests against other SSH > > implementations, here's a heads-up: > > > > https://twistedmatrix.com/trac/ticket/9422 > > > > TL;DR: commit 7c856857607112a3dfe6414696bf4c7ab7fb0cb3 caused there to > > be an SSH_MSG_DEBUG message sent where there wasn't one before, which > > tripped over an implementation bug in Twisted. I'm guessing slightly at > > the affected version range based on git history. > > Thanks for letting is know - we could set SSH_BUG_DEBUG to disable debug > messages f...

I don't see a problem, my MTU is at the default value = 1500, but when I look at the trace from libssh2, packet type 4 received, => SSH_MSG_DEBUG packet type 91 received, => SSH_MSG_CHANNEL_OPEN_CONFIRMATION packet type 93 received, => SSH_MSG_CHANNEL_WINDOW_ADJUST packet type 99 received, => SSH_MSG_CHANNEL_SUCCESS packet type 98 received, => SSH_MSG_CHANNEL_REQUEST packet type 96 received, => SSH_MSG_CHANNEL_EOF packet type...

...can be seen here: > --snip-- > $ ssh u at u 2>&1 | sed -n l > ssh: Could not resolve hostname u: Name or service not known\r$ > --snip-- > > I have seen section 11.3 from rfc4253, but am unsure whether that is > the origin of this behavior. Is a "Debug Message"(SSH_MSG_DEBUG) > considered anything that is logged on stderr? > > Any insights welcome! > > Cheers, > Josh > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-d...

I'm trying to send data to a server with openssh 7.9p1, but it's hanging somewhere. the client stop at the line : Jul 7 11:52:16 TOTO sshd[19553]: debug3: channel 0: will not send data after close and after 5 minutes the client closes the connection, why ? This is the trace of the server openssh : ( DEBUG3 level) Jul 7 11:52:15 TOTO sshd[31175]: debug3: fd 6 is not O_NONBLOCK Jul