Wireshark-bugs: [Wireshark-bugs] [Bug 10959] Wireshark doesn't parse options after IPv4 MTU Repl
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 15 Feb 2015 19:45:19 +0000

changed bug 10959


What Removed Added
CC   pascal.quantin@gmail.com

Comment # 2 on bug 10959 from 
Moreover in case of invalid length, which one should be used to jump to the
next option? The theoretical one, assuming that only the length field was badly
filled? Or the one indicated in the option (assuming that the packet contains
unauthorized padding)? I guess the latter could be the most meaningful but
could still fail depending on the initial error(typically it could lead to
weird things when fuzzing a capture).
Or we keep the current conservative approach: stopping dissection as soon as
something invalid is seen.

You are receiving this mail because:
  • You are watching all bug changes.