Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 9422] New: editcap does not correctly use the chop offset (fix included)

[bugzilla-daemon@xxxxxxxxxxxxx]

Bug ID	9422
Summary	editcap does not correctly use the chop offset (fix included)
Classification	Unclassified
Product	Wireshark
Version	SVN
Hardware	All
OS	All
Status	UNCONFIRMED
Severity	Normal
Priority	Low
Component	Extras
Assignee	bugzilla-admin@wireshark.org
Reporter	haggismn@gmail.com

Created attachment 12066 [details]
patch: editcap chop offset of 0 chops from the beginning, not the end of the
packet

Build Information:
Compiled (64-bit) with GLib 2.36.0, with libpcap, with libz 1.2.7, without
POSIX
capabilities, without libnl, without SMI, without c-ares, without ADNS, without
Lua, without Python, without GnuTLS, without Gcrypt, without Kerberos, without
GeoIP.

Running on Linux 3.8.0-32-generic, with locale en_GB.UTF-8, with libpcap
version
1.3.0, with libz 1.2.7.
      Intel(R) Xeon(R) CPU E3-1270 V2 @ 3.50GHz

Built using gcc 4.7.3.
--
When chopping bytes from the packet using the editcap -C option, the chopping
will always start from the end of the packet, unless an offset greater than 0
is specified.

The following 2 commands will chop from the end;
editcap -T ether -L -C 0:32 in.pcap out.pcap
editcap -T ether -L -C 32 in.pcap out.pcap

The following will chop correctly, as the offset is >0;
editcap -T ether -L -C 12:4 in.pcap out.pcap

The attached patch corrects this issue.

---

      You are receiving this mail because:

• You are watching all bug changes.