Wireshark-bugs: [Wireshark-bugs] [Bug 6964] New: USB: incorrect generated bInterfaceClass for co
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sat, 17 Mar 2012 10:19:42 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6964

           Summary: USB: incorrect generated bInterfaceClass for composite
                    device CONTROL transactions
           Product: Wireshark
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: bugzilla-admin@xxxxxxxxxxxxx
        ReportedBy: steve@xxxxxxxxxxxxxxx


Created attachment 8041
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=8041
Fix

Build Information:
wireshark 1.7.1 (SVN Rev 41627 from /trunk)

Copyright 1998-2012 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.24.8, with Cairo 1.10.2, with Pango 1.29.4, with
GLib 2.30.2, with libpcap, with libz 1.2.5, with POSIX capabilities (Linux),
with SMI 0.4.8, with c-ares 1.7.4, with Lua 5.1, without Python, with GnuTLS
2.12.14, with Gcrypt 1.5.0, with MIT Kerberos, with GeoIP, with PortAudio
V19-devel (built May  5 2011 11:00:51), without AirPcap.

Running on Linux 3.2.7-1.fc16.x86_64, with locale en_US.UTF-8, with libpcap
version 1.1.1, with libz 1.2.5, GnuTLS 2.12.14, Gcrypt 1.5.0.

Built using gcc 4.6.2 20111027 (Red Hat 4.6.2-1).

--
For CONTROL transactions, the generated bInterfaceClass tree item is
always set to the class of the last interface descriptor returned by
a GET CONFIGURATION request.

For standard CONTROL transactions (i.e. SET INTERFACE) this is merely
annoying, but for class-specific CONTROL transactions targeted to
interfaces or endpoints on composite devices it is truly incorrect
and prevents the proper class-specific dissector from being invoked.

The bug is seen easily when using a coloring rule based on 
usb.bInterfaceClass with transactions from a composite device.

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