| Bug ID |
8754
|
| Summary |
GSM Cell Broadcast dissector displays trailing \r padding characters
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.10.0
|
| Hardware |
x86
|
| OS |
All
|
| Status |
RESOLVED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
| CC |
[email protected]
|
| Status |
RESOLVED
|
| CC |
[email protected]
|
| Resolution |
DUPLICATE
|
Build Information:
wireshark 1.10.0rc2 (SVN Rev Unknown from unknown)
Copyright 1998-2013 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 (32-bit) with GTK+ 2.24.18, with Cairo 1.12.8, with Pango 1.32.5, with
GLib 2.34.3, with libpcap, with libz 1.2.7, without POSIX capabilities, without
libnl, without SMI, without c-ares, without ADNS, with Lua 5.1, without Python,
without GnuTLS, without Gcrypt, without Kerberos, without GeoIP, without
PortAudio, with AirPcap.
Running on Linux 3.7.10-1.11-default, with locale en_US, with libpcap version
1.3.0, with libz 1.2.7, without AirPcap.
Built using gcc 4.7.2 20130108 [gcc-4_7-branch revision 195012].
--
Using the attached cb-example.pcap together with Decode User DLT 0 as
gsm_cbs wireshark displays the CBS content with the trailing \r padding
where a mobile would only display S6-19,54773% .
Cell Broadcast Page Contents
CBS Page Content:
S6-19,54773%\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r
GSM Cell Broadcast Message
CBS Message Content:
S6-19,54773%\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r
In the long term gsm_sms_char_7bit_unpack should perhaps be extended with
a context (SMS, USSD, CB) parameter but for the time being the proposed
patch should be OK.
The patch is also applicable to the SVN trunk.
You are receiving this mail because:
- You are watching all bug changes.