PuTTY bug ssh-remoteid-minusone

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: Remote channel numbers of 0xffffffff will confuse PuTTY
class: bug: This is clearly an actual problem we want fixed.
difficulty: fun: Just needs tuits, and not many of them.
priority: medium: This should be fixed one day.
present-in: 2005-01-19
fixed-in: 2005-01-23 11bc6185ec4af518dc91600ba4aa85e94cc5f665 (0.58)

Within ssh.c, PuTTY uses a server channel number of (unsigned)(-1) to
represent a channel that doesn't have a server channel number assigned
yet.  Neither SSH-1 nor SSH-2, though, places any restriction on the use
of 0xffffffff as a channel number, which is what (unsigned)(-1) will
be on a 32-bit system.  If a server using 0xffffffff as a channel
number, PuTTY will not believe that the channel is properly open, and
will, for instance, die with a fatal error if the server tries to
close it.
Audit trail for this bug.

If you want to comment on this web site, see the Feedback page.
(last revision of this bug record was at 2016-12-27 11:40:22 +0000)