https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6984
--- Comment #3 from Martin Kaiser <wireshark@xxxxxxxxx> 2012-03-25 15:12:34 PDT ---
Hi Tyson and all,
you don't have to upload a working example. I have some small files here that
work ok for testing.
I've just checked HD-SD1-1SEG.ts
The hexdump of the start is
0000000: 471f ff10 ffff ffff ffff ffff ffff ffff G...............
[...]
00000b0: ffff ffff ffff ffff ffff ffff a12f ecdb ............./..
00000c0: ffff ffff 27ad e59c 2f11 894a 4701 1110 ....'.../..JG...
The file starts with 0x47 which is the start of a packet. 188 (0xbc) bytes
later, there must be the next packet, starting with 0x47 as usual. The wiretap
routine to detect mpeg2 ts checks for 10 consecutive packets. We read 0xa1
instead and reject the file. Surprisingly, the next 0x47 appears exactly 0x10
bytes too late.
Maybe there's bogus data at the beginning of the file or something dodgy
between the packets. The latter is certainly not allowed.
We might have to play with the mpeg detection routine if it turns out that
these strict checks are a problem.
Best regards,
Martin
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.