Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 5940] New: DVB-CI dissector: address checks for COR write

Date: Sat, 21 May 2011 03:49:18 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5940

           Summary: DVB-CI dissector: address checks for COR write
           Product: Wireshark
           Version: SVN
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: wireshark@xxxxxxxxx


Created an attachment (id=6370)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=6370)
patch against r37341 that adds two COR address checks

Build Information:
TShark 1.7.0 (SVN Rev 37333 from /trunk)

Copyright 1998-2011 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 GLib 2.16.6, with libpcap 0.9.8, with libz 1.2.3.3,
without POSIX capabilities, without libpcre, without SMI, without c-ares,
without ADNS, without Lua, without Python, with GnuTLS 2.4.2, with Gcrypt
1.4.1,
with MIT Kerberos, without GeoIP.

Running on Linux 2.6.29.1, with libpcap version 0.9.8, with libz 1.2.3.3.

Built using gcc 4.3.2.

--
the attached patch (against r37341) checks the address of the Configuration
Option Register that is used for switching a PC-Card in DVB-CI mode.

The address must be <= 0xffe. In my pcap definition
(http://www.kaiser.cx/pcap-dvbci.html), I defined 0xffff as "address unknown"
in case your DVB-CI capture tool can't figure out the COR address.

These two cases are checked by the patch. Thanks for feedback and/or merging
it.

   Martin

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.