PuTTY bug ext-data-at-start

This is a mirror. Follow this link to find the primary PuTTY web site.

Home | FAQ | Feedback | Licence | Updates | Mirrors | Keys | Links | Team
Download: Stable · Snapshot | Docs | Changes | Wishlist

summary: "unexpected packet type 95" with VShell 2.1.5
class: bug: This is clearly an actual problem we want fixed.
present-in: 0.53b
fixed-in: 2004-11-28 02b0474f578ec550552989bd6461fd7151609006 (0.58)

We've had one report of the error Unexpected response to shell/command request: packet type 95 when connecting to VShell 2.1.5 with PSCP.

Packet type 95 is SSH2_MSG_CHANNEL_EXTENDED_DATA. Perhaps this is VShell complaining on stderr about a nonexistent SFTP server subsystem, or similar?

This seems likely to have the same root cause as portfwd-at-start: brittle code at connection startup.

Ref. <>

SGT, 2004-11-27: I've rearchitected the SSH back end somewhat, so that it's now a hybrid of coroutine-based sequential code and random dispatch-table handling of incoming packets. This ought to solve this problem, although I'm unable to immediately test it.

If you want to comment on this web site, see the Feedback page.
Audit trail for this bug.
(last revision of this bug record was at 2017-04-28 16:52:45 +0100)