PuTTY semi-bug winadj-success

This is a mirror. The primary PuTTY web site can be found here.

Home | Licence | FAQ | Docs | Download | Keys | Links
Mirrors | Updates | Feedback | Changes | Wishlist | Team

summary: Bombing out with 'Received SSH_MSH_CHANNEL_SUCCESS for "winadj@putty.projects.tartarus.org"'
class: semi-bug: This might or might not be a bug, depending on your precise definition of what a bug is.
priority: high: This should be fixed in the next release.
absent-in: 0.60
present-in: 2008-03-28 2008-12-01

We've had a few reports of SSH connections bombing out with the following error message, reportedly under heavy load:

PuTTY Fatal Error

(X)  Disconnected: Received SSH_MSH_CHANNEL_SUCCESS for
     "winadj@putty.projects.tartarus.org"

                      [   OK   ]

Reports:

This message has only existed in PuTTY since the 'flow-control' feature was implemented, which was after we released 0.60; so at the time of writing, only people using development snapshots, or third-party code incorporating development code, should be seeing this. We probably want to find out what's going on before we make a release with this feature in.

On the face of it, it looks like the SSH server is incorrectly responding to our unilaterally-defined channel request message with SUCCESS, which it should never do since it's something we made up. (Our documentation mandates a FAILURE response, but that's only a restatement of the RFC 4254 requirement for a FAILURE response to requests that aren't understood -- we don't expect any server to specifically handle this message.)

However, perhaps we're getting confused about the mapping of requests to responses, or something.

Audit trail for this semi-bug.


If you want to comment on this web site, see the Feedback page.
(last revision of this bug record was at 2008-12-01 20:28:35 +0000)