]> asedeno.scripts.mit.edu Git - PuTTY.git/commit - doc/config.but
Implement this year's consensus on CHANNEL_FAILURE vs CHANNEL_CLOSE.
authorSimon Tatham <anakin@pobox.com>
Sun, 6 Jul 2014 14:05:39 +0000 (14:05 +0000)
committerSimon Tatham <anakin@pobox.com>
Sun, 6 Jul 2014 14:05:39 +0000 (14:05 +0000)
commitaaaf70a0fc0f071b9e9c6a51606c78b16a464841
tree903e64a54c76aa6e2bc7dd6c92e89fb2d22ca265
parent3d337b49ef55358a9db692696c9a28e9fc146de3
Implement this year's consensus on CHANNEL_FAILURE vs CHANNEL_CLOSE.

We now expect that after the server has sent us CHANNEL_CLOSE, we
should not expect to see any replies to our outstanding channel
requests, and conversely after we have sent CHANNEL_CLOSE we avoid
sending any reply to channel requests from the server. This was the
consensus among implementors discussing the problem on ietf-ssh in
April 2014.

To cope with current OpenSSH's (and perhaps other servers we don't
know about yet) willingness to send request replies after
CHANNEL_CLOSE, I introduce a bug-compatibility flag which is detected
for every OpenSSH version up to and including the current 6.6 - but
not beyond, since https://bugzilla.mindrot.org/show_bug.cgi?id=1818
promises that 6.7 will also implement the new consensus behaviour.

[originally from svn r10200]
config.c
doc/config.but
putty.h
settings.c
ssh.c
windows/winhelp.h