I've written a bug up on this (bug #1132). I believe the culprit is a
combination of the SSL dissector and the http dissector.
-Brian
Brian Vandenberg wrote:
>> IIRC there's a call to col_set_writable(.., FALSE)
>> somewhere in dissector-http.c
>>
>>
> Thanks for the tip, I had figur
>
> IIRC there's a call to col_set_writable(.., FALSE)
> somewhere in dissector-http.c
>
>
Thanks for the tip, I had figured out that it wasn't writable, but I
hadn't [yet] found where it was being set to not writable. I'm slowly
narrowing in on this, so hopefully I'll know what's causing t
I've written a bug up on this (bug #1132). I believe the culprit is a
combination of the SSL dissector and the http dissector.
-Brian
Brian Vandenberg wrote:
>> IIRC there's a call to
>> col_set_writable(.., FALSE)
>> somewhere in dissector-http.c
>>
>>
>>
> Thanks for the tip, I
>
> IIRC there's a call to
> col_set_writable(.., FALSE)
> somewhere in dissector-http.c
>
>
Thanks for the tip, I had figured out that it wasn't writable, but I
hadn't [yet] found where it was being set to not writable. I'm slowly
narrowing in on this, so hopefully I'll know what's causi
Ulf,
Certain of it. My protocol tree gets created and added below the http
tree. In addition, if I remove my plugin from the plugins folder and
run wireshark and open the pcap file I'm using for testing I see the
exact same behavior: the http response packets still show up as TLSv1
packets
Hi,
Le mercredi 27 septembre 2006 à 09:08 -0600, Brian Vandenberg a écrit :
> I'm writing a dissector that relies on the http dissector. The
> server's I'll be monitoring use ssl, so there's a requirement to use the
> ssl dissector to decrypt the packets and hand them off to the http
> dissec
Brian Vandenberg wrote:
> I'm writing a dissector that relies on the http dissector. The
> server's I'll be monitoring use ssl, so there's a requirement to use the
> ssl dissector to decrypt the packets and hand them off to the http
> dissector.
>
> Requests & responses are both treated pro
I'm writing a dissector that relies on the http dissector. The
server's I'll be monitoring use ssl, so there's a requirement to use the
ssl dissector to decrypt the packets and hand them off to the http
dissector.
Requests & responses are both treated properly during dissection, so
that i
