PuTTY bug portfwd-corrupt

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

summary: Reports of port forwarding corruption
class: bug: This is clearly an actual problem we want fixed.
priority: high: This should be fixed in the next release.
present-in: 0.53b 2003-06-29 0.54 0.58

We've had several reports of data corruption in port-forwarded connections. Some (possibly all) of these are due to data loss. The PuTTY client (as opposed to others) appears to be correlated with the data loss, although it's unclear whether the data is actually being lost before or after PuTTY is dealing with it.

Problems have been reported with both directions of tunneling, both directions of data transfer, and both SSH protocols (SSH-1 and SSH-2).

Update, 2005-06-15: I (JTN) have reproduced loss of trailing data with a remote-to-local SSH-2 port forwarding, where a burst data is sent from remote to local followed immediately by EOF. I suspect that PuTTY's lack of support for half-closed connections is to blame in at least this case. Update, 2011-09-13: I (SGT) have just (hopefully) fixed the half-closed issue, so perhaps that will be improved now.

The reports below may correspond to several different bugs, as a range of symptoms are reported.

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 2011-09-14 10:45:56 +0000)