If the SSH server sends us CHANNEL_CLOSE for a channel on which we're
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sun, 21 Jul 2013 10:12:58 +0000 (10:12 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Sun, 21 Jul 2013 10:12:58 +0000 (10:12 +0000)
commitdf9888023b27a5d24c16ed857a10f391b440bd42
treeed0e59a663626a3512f9dc2a78208a6ec8e3d651
parente354075ee40880f5df252ac85538922a97f2d5e3
If the SSH server sends us CHANNEL_CLOSE for a channel on which we're
sitting on a pile of buffered data waiting for WINDOW_ADJUSTs, we
should throw away that buffered data, because the CHANNEL_CLOSE tells
us that we won't be receiving those WINDOW_ADJUSTs, and if we hang on
to the data and keep trying then it'll prevent ssh_channel_try_eof
from sending the CHANNEL_EOF which is a prerequisite of sending our
own CHANNEL_CLOSE.

git-svn-id: svn://svn.tartarus.org/sgt/putty@9953 cda61777-01e9-0310-a592-d414129be87e
ssh.c