, June 05, 2007 10:32 PM
To: Kukosa, Tomas
Subject: Re: [Wireshark-dev] help needed in tracking down a bug in SSL dissector
Tomas,
Not a problem. Oh, and I meant TLSv1 (was thinking SSL3).
The IP is 192.168.20.68, the port is 9091, and I've attached two key
files. I'm unsure wh
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] help needed in tracking down a bug in SSL dissector
>
> I found a bug about 9-10 months ago in the SSL dissector that was
> never fixed, so I'm trying to find/fix the problem myself, but I'm
> having
: Thursday, May 31, 2007 12:40 AM
To: Developer support list for Wireshark
Subject: [Wireshark-dev] help needed in tracking down a bug in SSL dissector
I found a bug about 9-10 months ago in the SSL dissector that was
never fixed, so I'm trying to find/fix the problem myself, but I'm
having a
As an addendum to this, one thing I tried for tracking this down was
to set a conditional breakpoint to watch for each instance of an
execution of add_new_data_source where the name of the data source
contains the text "Reassembled SSL", then set a watch for
tvb->real_data+c, for some c that
I found a bug about 9-10 months ago in the SSL dissector that was
never fixed, so I'm trying to find/fix the problem myself, but I'm
having a hard time tracking it down.
Essentially this is what happens:
* POST to server occurs, the SSL chunk isn't fragmented.
* When SSL dissector decrypts
