Re: tshark doesn't print bytes following a NULL character? (v1.2.6)

[Guy Harris <guy () alum mit edu>]

On Aug 30, 2010, at 6:48 AM, Ryan Lynch wrote:

> If it's a bug, I assume it's related to some assumptions about
> null-terminated strings in C.

It's related to the fact that libwireshark - as used both by TShark and Wireshark - currently represents all strings in 
packets as C strings.  They should probably be represented as a counted UTF-8 string or as a counted byte sequence plus 
a character encoding or something such as that.
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe