https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5509
--- Comment #3 from Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx> 2010-12-20 16:17:29 MST ---
Thanks for the report. When I wrote the commview code for Wireshark, I made
the heuristics to see if it is a commview file very specific (perhaps too
specific) as you can see from this code snippet from wiretap/commview.c:
/* If any of these fields do not match what we expect, bail out. */
if(cv_hdr.version != 0 ||
cv_hdr.year < 1970 || cv_hdr.year >= 2038 ||
cv_hdr.month < 1 || cv_hdr.month > 12 ||
cv_hdr.day < 1 || cv_hdr.day > 31 ||
cv_hdr.hours > 23 ||
cv_hdr.minutes > 59 ||
cv_hdr.seconds > 60 ||
cv_hdr.signal_level > 100 ||
(cv_hdr.direction != 0x00 && cv_hdr.direction != 0x01 &&
cv_hdr.direction != 0x02) ||
(cv_hdr.flags & FLAGS_RESERVED) != 0 ||
((cv_hdr.flags & FLAGS_MEDIUM) != MEDIUM_ETHERNET &&
(cv_hdr.flags & FLAGS_MEDIUM) != MEDIUM_WIFI &&
(cv_hdr.flags & FLAGS_MEDIUM) != MEDIUM_TOKEN_RING) ||
cv_hdr.reserved != 0)
return 0; /* Not our kind of file */
I'll see if I can spot the change with a hex editor.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.