Wireshark-bugs: [Wireshark-bugs] [Bug 5562] New: Opaque Data Syncml 1.2 tags not decoded in Pack
Date: Mon, 10 Jan 2011 04:14:27 -0800 (PST)

           Summary: Opaque Data Syncml 1.2 tags not decoded in Packet
           Product: Wireshark
           Version: 1.4.2
          Platform: x86
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: [email protected]
        ReportedBy: [email protected]

Created an attachment (id=5709)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=5709)
Packet #2 shows opaque data is not being decoded in the Packet Details

Build Information:
Version 1.4.3pre1-35179 (SVN Rev 35179 from /trunk-1.4)

Copyright 1998-2010 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO

Compiled (32-bit) with GTK+ 2.16.6, with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
12 2010), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.2
(packet.dll version, based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, without AirPcap.

Built using Microsoft Visual C++ 9.0 build 30729
Opaque Data Syncml 1.2 tags are not being decoded in Packet Details.  
i.e: c3 (opaque data) 06 (6 bytes) 44 4d 2f 31 2e 32 (DM/1.2) 
is shown as: (6 bytes of opaque data) 
instead of DM/1.2 
Data is shown in the Packet Bytes window (since its plain text), but not in the
Packet Details, which is kind of bothersome. I tried with Wireshark 1.4.2 and
1.4.3pre1-35179 without any success.

Since the WBXML Token Description already shows it is Opaque data, it would be
very useful to show the ASCII representation in the Rendering field of the Data
Representation. Anyway I understand its Opaque Data, and its not supposed to be
string. This enhancement would be a guess that could be more useful than "X
bytes of opaque data".

WAP Binary XML Content Format
Opaque Data

opaque = OPAQUE length *byte

The opaque token (OPAQUE) encodes application-specific data. A length field and
zero or more bytes of data follow the token. The length field encodes the
number of bytes of data, excluding the OPAQUE token and the length field.

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