https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5344
Summary: wireshark tools do not detect and read some ERF files
correctly
Product: Wireshark
Version: SVN
Platform: Other
OS/Version: All
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: stephen@xxxxxxxxxx
Build Information:
wireshark 1.5.0 (SVN Rev 34646 from /trunk)
Copyright 1998-2010 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.22.0, with GLib 2.26.0, with libpcap 1.1.1, with
libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8,
with c-ares 1.7.3, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt
1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Aug 3
2010 06:06:51), without AirPcap.
Running on Linux 2.6.35-22-generic, with libpcap version 1.1.1, with libz
1.2.3.4, GnuTLS 2.8.6, Gcrypt 1.4.5.
Built using gcc 4.4.5.
--
The wiretap heuristic for detecting for ERF files fails if the first record in
the file is an ERF_TYPE_PAD record. The PAD record is skipped, but its '0' time
stamp is subsequently used in the 'no time stamp deltas > 2 weeks' heuristic
which fails and the file is rejected.
Also erf_read() in wiretap fails to handle ERF_TYPE_PAD records with rlen != 16
correctly. This may cause garbage to be read and wireshark may exit. These
records are valid but rare.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
