Wireshark · Wireshark-dev: [Wireshark-dev] pcapng, must opt

Wireshark-dev: [Wireshark-dev] pcapng, must opt_comment string be 0-terminated?

From: Martin Kaiser <lists@xxxxxxxxx>

Date: Mon, 2 Jan 2012 00:00:40 +0100

Dear all,

happy new year to all of you.

In a pcapng file, does the string stored in an opt_comment option have
to be 0-terminated? I couldn't find anything explicit about this in the
specification. Pcapng options have a length field, therefore I'd guess
the 0 termination is not required. What do you think?

Best regards,

   Martin

Follow-Ups:
- Re: [Wireshark-dev] pcapng, must opt_comment string be 0-terminated?
  - From: Guy Harris

Prev by Date: Re: [Wireshark-dev] [Wireshark-commits] rev 40352: /trunk/ /trunk/macosx-support-lib-patches/: glib-pkgconfig.patch /trunk/: macosx-setup.sh
Next by Date: Re: [Wireshark-dev] pcapng, must opt_comment string be 0-terminated?
Previous by thread: Re: [Wireshark-dev] [Wireshark-commits] rev 40321: /trunk/ /trunk/epan/: base64.h epan.h epan_dissect.h ex-opt.h prefs.h strutil.h timestamp.h tvbuff.h /trunk/gtk/: recent.h /trunk/: airpcap_loader.h capture-pcap-util.h capture-wpcap.h capture.h ...
Next by thread: Re: [Wireshark-dev] pcapng, must opt_comment string be 0-terminated?
Index(es):
- Date
- Thread