forked from osmocom/wireshark
0773147a55
Change the data structure for that option to have a type field, indicating that it's either a pcap filter string or a BPF program, followed by a union with a string-pointer member for pcap filter strings and an instruction-count-and-pointer-to-instructions structure for BPF programs. Have routines to add, set, and fetch that option that handle that structure; discard the "generic structured option" routines. That means there's more type checking possible at compile time. Add more code to handle BPF programs. When writing pcapng files, check, both for that option and for string options, whether the option length is too big for the data to fit in a pcapng option, and don't write it if it is. (XXX - truncate the data? Report an error?) |
||
---|---|---|
.. | ||
patches | ||
po | ||
source | ||
tests | ||
README.Debian | ||
README.Debian.security | ||
changelog | ||
compat | ||
control | ||
copyright | ||
dirs | ||
ethereal-common.NEWS | ||
headers-check.c | ||
libwireshark-data.install | ||
libwireshark-dev.install | ||
libwireshark0.install | ||
libwireshark0.lintian-overrides | ||
libwireshark0.symbols | ||
libwiretap-dev.install | ||
libwiretap0.docs | ||
libwiretap0.install | ||
libwiretap0.symbols | ||
libwsutil-dev.install | ||
libwsutil0.install | ||
libwsutil0.symbols | ||
license-text-about-dialog | ||
maxmind_db_paths | ||
postinst | ||
rules | ||
templates | ||
tshark.docs | ||
tshark.install | ||
tshark.lintian-overrides | ||
tshark.manpages | ||
wireshark-common.config | ||
wireshark-common.install | ||
wireshark-common.lintian-overrides | ||
wireshark-common.manpages | ||
wireshark-common.postinst | ||
wireshark-common.postrm | ||
wireshark-dev.docs | ||
wireshark-dev.install | ||
wireshark-dev.manpages | ||
wireshark-dev.prerm | ||
wireshark-doc.docs | ||
wireshark-qt.docs | ||
wireshark-qt.install | ||
wireshark-qt.lintian-overrides | ||
wireshark-qt.manpages |
README.Debian.security
Handling security fixes in source package wireshark Wireshark is a network protocol analyzer and it's ability to perform deep packet inspection in live traffic may encourage users to use Wireshark/Tshark as a part of an intrusion detection or traffic monitoring system. In that case, please note that Wireshark/Tshark may contain remotely triggerable bugs causing crashes or allowing code injection. Bugs allowing code injection will be fixed in regular Debian Security Advisories, but fixes for pure crash bugs may be delayed. -- Balint Reczey <balint@balintreczey.hu> Fri, 10 Jul 2009 15:38:33 +0200