In SSH packet logging mode, log SSH-2 packet sequence numbers, in
authorsimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Tue, 11 Nov 2008 07:47:27 +0000 (07:47 +0000)
committersimon <simon@cda61777-01e9-0310-a592-d414129be87e>
Tue, 11 Nov 2008 07:47:27 +0000 (07:47 +0000)
commit0d13bfcd3dc0eac74361d98a550092ffa054e918
tree569c76712122b0cfed7aa9fac14a5c042b20114c
parent5025a9931265fe959126155737a04ec8f8f686aa
In SSH packet logging mode, log SSH-2 packet sequence numbers, in
both directions. We had a bug report yesterday about a Cisco router
sending SSH2_MSG_UNIMPLEMENTED and it wasn't clear for which packet;
logging the sequence numbers should make such problems much easier
to diagnose.

(In fact this logging fix wouldn't have helped in yesterday's case,
because the router also didn't bother to fill in the sequence number
field in the SSH2_MSG_UNIMPLEMENTED packet! This is a precautionary
measure against the next one of these problems.)

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