| Bug ID |
13032
|
| Summary |
X.400 email subject showing \357\277\275 for valid T.61 characters in Packet Details pane
|
| Product |
Wireshark
|
| Version |
2.3.x (Experimental)
|
| Hardware |
x86
|
| OS |
Windows Server 2008 R2
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 15002 [details]
Contains P22 email packet #10
Build Information:
Version 2.3.0-928-gbdd2193 (v2.3.0rc0-928-gbdd2193 from master)
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 GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares
1.12.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Oct 4 2016), with
AirPcap.
Running on 64-bit Windows Server 2008R2 Service Pack 1, build 7601, with
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 8191 MB of physical
memory, with locale English_United Kingdom.1252, with WinPcap version 4.1.3
(packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without AirPcap.
Built using Microsoft Visual C++ 12.0 build 40629
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
A P22 X.420 object shows the subject as:
subject: Subject with non-Teletext chars
"\357\277\275\357\277\275??????\357\277\275" in the packet details pane. The
subject shown in the packet list pane is correct (albeit octal!).
The hex packet display is also correct, showing the valid T.61 characters (a6,
a4, a3 in this case)
Packet #10 in the attached trace shows the issue.
You are receiving this mail because:
- You are watching all bug changes.