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

[Ryan Lynch <ryan.b.lynch () gmail com>]

On Mon, Aug 30, 2010 at 12:55, Guy Harris <guy () alum mit edu> wrote:
> 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.

Thanks for the answer, Guy. That makes sense.

A search through the bug tracker and found this:

 * https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1372

Sounds like a pretty big project. Do you know whether there's any
active development effort going into this, right now?

-Ryan
___________________________________________________________________________
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