Bug ID |
13150
|
Summary |
Issue on tshark json/ek output. Keys duplicated
|
Product |
Wireshark
|
Version |
2.2.0
|
Hardware |
x86
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
TShark (Wireshark) 2.3.0-1376-g9e2a9d0 (Git Rev Unknown from unknown)
Copyright 1998-2016 Gerald Combs <[email protected]> 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 libpcap, without POSIX capabilities, without libnl, with
GLib 2.40.2, with zlib 1.2.8, without SMI, without c-ares, without Lua, without
GnuTLS, without Gcrypt, without Kerberos, without GeoIP, without nghttp2,
without LZ4, without Snappy.
Running on Linux 3.13.0-46-generic, with Intel(R) Core(TM) i7-3610QM CPU
@
2.30GHz (with SSE4.2), with 16008 MB of physical memory, with locale
en_US.UTF-8, with libpcap version 1.5.3, with zlib 1.2.8.
Built using gcc 4.8.2.
--
Hi,
I noticed that using tshark json/ek output that sometimes keys are duplicated.
It won't work on almost all programming languages since keys are expected to be
unique. Instead of duplicating the key, a solution would have been to transform
the values into an array of values for the one unique key.
Examples can be seen on SIGTRAN messages where multiple gsm_map parts are
present on the same packet.
See: https://tools.ietf.org/html/rfc7159#section-4
You are receiving this mail because:
- You are watching all bug changes.