Tera Term, Unexpected SSH2 message(80) on current stage(6) [was Re: SAP-2015-3-1 issues]

Darren Tucker dtucker at zip.com.au
Thu Apr 9 12:39:58 AEST 2015

On Thu, Apr 9, 2015 at 11:44 AM, Bryan Drewery <bryan at shatow.net> wrote:
> Received disconnect from 11: Unexpected SSH2 message(80) on
> current stage(6)

Message type 80 is SSH_MSG_GLOBAL_REQUEST, and RFC4254 section 4 says "Note
that both the client and server MAY send global requests at any time, and
the receiver MUST respond appropriately."

Any idea what the message is?  It'd be nice if the client showed the whole
packet, but failing that you could build a server with "./configure
--with-cflags=-DPACKET_DEBUG" then pick the packet out of the server-side
debug logs.

The only global message I can think of is the protocol keepalives, in which
case you could try setting "ClientAliveInterval 0" in sshd_config to see if
that helps.

Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

More information about the openssh-unix-dev mailing list