Hi,
I think your solution is not workaround but quite standard solution in
Wireshark.
As it is not guaranteed that you have captured whole SSL session it is
better to have good heuristic than to relay upon state information.
Mailcode: NdD2sKHg
-Original Message-
From: [EMAIL PROTECTED]
[
Todd Vollmer wrote:
> Sorry for the repost. The wiki doesn't mention putting PATCH in the
> subject line and I am new here.
>
> I have attached a patch for the protocol hierarchy statistics (-z io,
> phs). It's a simple update from a 32 bit unsigned integer to a 64 bit
> version. I am a little u
Here is the dissector I mentioned before.
Most opcodes are not yet implemented, but the dissector is in a
usefull state already.
We need it for a tshark running 24/7:
tshark -i eth0 -R gdsdb.prepare.statement
So we will be able to monitor an external application using the database.
As far as I k
