Rather than rejecting spurious SSH_MSG_CHANNEL_SUCCESSes, and ignoring
authorben <ben@cda61777-01e9-0310-a592-d414129be87e>
Mon, 1 Oct 2007 21:11:11 +0000 (21:11 +0000)
committerben <ben@cda61777-01e9-0310-a592-d414129be87e>
Mon, 1 Oct 2007 21:11:11 +0000 (21:11 +0000)
commit837d6ba65e2511747da1c8e5a096f59d1f48c475
tree87e34f62f9e070442327e956b64e0cab205d4870
parente223b7c7fb42431f9d4f7111c5df209d6b8b1d25
Rather than rejecting spurious SSH_MSG_CHANNEL_SUCCESSes, and ignoring
spurious SSH_MSG_CHANNEL_FAILUREs, treat them as the protocol errors
they are and forcibly disconnect.  Inspired by recent traffic on
comp.security.ssh.

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