https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16129
Bug ID: 16129
Summary: [Regression] FT_CHAR fields not supported in Lua API
Product: Wireshark
Version: 3.0.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: Major
Priority: Low
Component: Dissection engine (libwireshark)
Assignee: bugzilla-ad...@wireshark.org
Reporter: nicolas.roy-renau...@ens.etsmtl.ca
Target Milestone: ---
Created attachment 17406
--> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=17406&action=edit
Test USB dissector that exhibits the problem
Build Information:
Wireshark 3.0.4 (Git commit 71591544b8d6)
Copyright 1998-2019 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.13.1, with libpcap, with POSIX capabilities
(Linux),
with libnl 3, with GLib 2.62.0, with zlib 1.2.11, without SMI, with c-ares
1.15.0, with Lua 5.2.4, with GnuTLS 3.6.9 and PKCS #11 support, with Gcrypt
1.8.5, with MIT Kerberos, with MaxMind DB resolver, with nghttp2 1.39.2, with
LZ4, with Snappy, with libxml2 2.9.9, with QtMultimedia, with SBC, with
SpanDSP,
with bcg729.
Running on Linux 5.3.1-arch1-1-ARCH, with Intel(R) Xeon(R) CPU E3-1230 V2
@ 3.30GHz (with SSE4.2), with 32134 MB of physical memory, with locale
LC_CTYPE=en_US.UTF-8, LC_NUMERIC=fr_CA.UTF-8, LC_TIME=fr_CA.UTF-8,
LC_COLLATE=en_US.UTF-8, LC_MONETARY=fr_CA.UTF-8, LC_MESSAGES=en_US.UTF-8,
LC_PAPER=fr_CA.UTF-8, LC_NAME=en_US.UTF-8, LC_ADDRESS=en_US.UTF-8,
LC_TELEPHONE=en_US.UTF-8, LC_MEASUREMENT=fr_CA.UTF-8,
LC_IDENTIFICATION=en_US.UTF-8, with libpcap version 1.9.0-PRE-GIT (with
TPACKET_V3), with GnuTLS 3.6.9, with Gcrypt 1.8.5, with zlib 1.2.11, binary
plugins supported (0 loaded).
Built using gcc 9.1.0.
--
Wireshark 2.4 onwards introduced the FT_CHAR type for dissectors
(https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=d7fe514fc05e95e3a99fd211768de5abdc3f6486),
which replaces FT_UINT8 in a number of places. FT_CHAR, unlike FT_UINT8, is not
supported in the Lua dissector API, so this breaks any dissector that relied on
a field with such a type, namely the USB URB type field for USB dissectors.
I was working on one such project back in early 2017, and after some time,
without any changes to my code, it stopped working. I did not realize what the
cause was (updating to Wireshark 2.4) until recently due to how vague the error
message was (it only says "Lua Error: test.lua:14: FT_ not yet supported" with
no mention of the type, and I thought type 3 means FT_UINT8).
Steps to reproduce:
1. Run the attached dissector against the attached capture data
2. Look at the expert information messages.
Current behavior:
The dissector does not run and the expert information logs "Lua Error:
test.lua:14: FT_ not yet supported" for nearly all packets.
Expected behavior:
The dissector should run properly (and output nothing).
--
You are receiving this mail because:
You are watching all bug changes.___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
