Fix `disconnect': arrange that we keep track of when we're expecting
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Tue, 11 Jan 2005 19:33:41 +0000 (19:33 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Tue, 11 Jan 2005 19:33:41 +0000 (19:33 +0000)
commitac9349657257bc48e24a5b932778bc2977d7bed6
treea808e51038f2e2185ab060edc637e3c78a146b6f
parente12d95a5afd186f7fd671944eb964496a2da0a77
Fix `disconnect': arrange that we keep track of when we're expecting
to see the server slam the TCP connection shut (i.e. almost never,
unless it's just sent us an SSH_MSG_DISCONNECT), and treat an
unexpected closure as a non-clean session termination. Previously
any server-initiated connection closure was being treated as a clean
exit, which was a hangover from the good old Telnet-only days.

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