]> asedeno.scripts.mit.edu Git - PuTTY.git/commit
projects / PuTTY.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a34ab9b) | patch
<1112163342.018492.101240@f14g2000cwb.googlegroups.com> on
authorSimon Tatham <anakin@pobox.com>
Wed, 30 Mar 2005 08:27:54 +0000 (08:27 +0000)
committerSimon Tatham <anakin@pobox.com>
Wed, 30 Mar 2005 08:27:54 +0000 (08:27 +0000)
commit6df09c6275274eb6a13adaad5b5df4a974f26ca0
tree83d1ae9f8c201139431f60a818a93be538a15d80tree | snapshot
parenta34ab9bfc9c2f1b62f06432ba14949262d3ff2ffcommit | diff
<1112163342.018492.101240@f14g2000cwb.googlegroups.com> on
comp.security.ssh contains a Dr Watson log which looks to me as if
`unclean-close-crash' occurred due to a rekey timer going off after
the session had closed. Hence, ssh2_timer() now avoids doing
anything if the session is already closed, and also ssh_do_close()
proactively calls expire_timer_context(). Between those I think they
ought to solve the problem.

[originally from svn r5564]
ssh.c diff | blob | history
local copy of git://git.tartarus.org/simon/putty.git