https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6673
Guy Harris <guy@xxxxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Guy Harris <guy@xxxxxxxxxxxx> 2011-12-15 00:23:19 PST ---
If stuff above the Wiretap library can't handle packet reported lengths >
WTAP_MAX_PACKET_SIZE, either that should be caught above the per-file-type
layer in Wiretap or should be handled by the caller.
We've recently fixed at least one problem with reported lengths > 2^31 - 1 (by
clamping the length to 2^31 - 1), so let's just remove the check from the
pcap-NG reader, to squelch some complaints we're getting from the buildbot (bug
6673 and its duplicates).
(The pcap reader uses it to cope with some of the botched libpcap formats that
changed the per-packet header without changing the magic number; I'll look at
trying to preserve those heuristics while still allowing reported lengths >
WTAP_MAX_PACKET_SIZE.)
Fixed in rev 40207.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.