Wireshark mailing list archives
Re: Hierarchy of fields & offsets
From: Guy Harris <guy () alum mit edu>
Date: Tue, 25 Jul 2017 15:45:06 -0700
On Jul 25, 2017, at 3:26 PM, Sultan, Hassan via Wireshark-dev <wireshark-dev () wireshark org> wrote:
Any reason why this is done in this way?
I don't know, but, whatever it is, it's not a *good* reason. Perhaps they didn't know how to handle a request whose length isn't known until you finish dissecting it. The answer is "give it an initial length of -1, to cover the rest of the data, and then set the length at the end"; I've changed the MySQL dissector in the master and 2.4 branches to do that. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Hierarchy of fields & offsets Sultan, Hassan via Wireshark-dev (Jul 25)
- Re: Hierarchy of fields & offsets Guy Harris (Jul 25)
- Re: "[UNVERIFIED SENDER]Re: Hierarchy of fields & offsets Sultan, Hassan via Wireshark-dev (Jul 25)
- Re: Hierarchy of fields & offsets Guy Harris (Jul 25)
- Re: "[UNVERIFIED SENDER]Re: Hierarchy of fields & offsets Sultan, Hassan via Wireshark-dev (Jul 25)
- Re: "[UNVERIFIED SENDER]Re: Hierarchy of fields & offsets Guy Harris (Jul 25)
- Re: "[UNVERIFIED SENDER]Re: "[UNVERIFIED SENDER]Re: Hierarchy of fields & offsets Sultan, Hassan via Wireshark-dev (Jul 27)
- Re: "[UNVERIFIED SENDER]Re: Hierarchy of fields & offsets Sultan, Hassan via Wireshark-dev (Jul 25)
- Re: Hierarchy of fields & offsets Guy Harris (Jul 25)