| Bug ID |
11558
|
| Summary |
allow longer pcap-ng comments
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
x86
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
bugzilla-admin@wireshark.org
|
| Reporter |
johannes@sipsolutions.net
|
Build Information:
Wireshark 1.99.10 (v1.99.10rc0-269-g6ac0d846ecc1 from master)
Copyright 1998-2015 Gerald Combs <gerald@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 GTK+ 3.16.4, with Cairo 1.14.2, with Pango 1.36.8, with
libpcap, with POSIX capabilities (Linux), with libnl 3, with libz 1.2.8, with
GLib 2.44.1, without SMI, without c-ares, without ADNS, with Lua 5.2, with
GnuTLS 3.3.15, with Gcrypt 1.6.3, without Kerberos, with GeoIP, without
PortAudio, without AirPcap.
Running on Linux 3.16.0-4-amd64, with locale en_GB.UTF-8, with libpcap version
1.7.3, with libz 1.2.8, with GnuTLS 3.3.15, with Gcrypt 1.6.3.
Intel(R) Core(TM) i7-3667U CPU @ 2.00GHz (with SSE4.2)
Built using gcc 5.2.1 20150903.
--
I have some tools where long pcap-ng comments are generated. It'd be possible,
in theory, to give those some extra file format, but as the data is pretty much
unstructured (the structure varies a lot) it's much easier to just output it as
text.
It'd therefore be great to allow longer pcapng comments to be displayed,
they're truncated at 240 bytes.
If somebody has some pointers how that might be possible (preferably without
increasing ITEM_LABEL_LENGTH) I'd take a stab at implementing it.
You are receiving this mail because:
- You are watching all bug changes.
