| Bug ID |
11673
|
| Summary |
PacketBB (RFC5444) dissector displays Tail as Head
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13969 [details]
capture of a packetBB packet illustrating the issue
Build Information:
Version 1.12.1 (Git Rev Unknown from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> 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+ 3.14.12, with Cairo 1.14.2, with Pango 1.36.8, with
GLib 2.44.0, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without Python,
with GnuTLS 3.3.8, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), without AirPcap.
Running on Linux 3.19.0-31-generic, with locale en_GB.UTF-8, with libpcap
version 1.6.2, with libz 1.2.8, GnuTLS 3.3.8, Gcrypt 1.6.2.
Intel(R) Core(TM)2 Duo CPU E7500 @ 2.93GHz
Built using gcc 4.9.2.
--
Hi,
I'd like to report a bug in the PacketBB (RFC5444) Dissector. I've found that
when displaying the contents of a RFC5444 message containing an address block
which has
* no head (i.e. the ahashead flag is 0)
* an all-zero tail (i.e. the ahaszerotail flag is 1)
the tail length value is incorrectly displayed as
Head: <value of tail-length>
while it should say:
Tail: <value of tail-length>
I've attached a capture of such a packet for reference.
Henning Rogge, the author of the packetbb dissector, was kind enough to have a
look at it and, after confirming that this was indeed not the correct
behaviour, sent me a patch, which I've pasted into this gist:
https://gist.github.com/anonymous/1765878af04c6c72c022 since I can't seem to
add two attachments. I've tested the patch on my machine and it resolves the
issue for me.
Best regards,
Lotte
You are receiving this mail because:
- You are watching all bug changes.
