forked from osmocom/wireshark
2dad30897b
We went with the whole WS_DLL_EXPORT thing so that we don't *have* to maintain lists of exported symbols; is there truly no way to automate the generation of *these* files? Change-Id: I77f240c77782ed634e4620833f951c4a02fb4390 Reviewed-on: https://code.wireshark.org/review/3083 Reviewed-by: Guy Harris <guy@alum.mit.edu> |
||
---|---|---|
.. | ||
patches | ||
po | ||
source | ||
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.symbols | ||
libwiretap-dev.install | ||
libwiretap0.docs | ||
libwiretap0.install | ||
libwiretap0.symbols | ||
libwsutil-dev.install | ||
libwsutil0.install | ||
libwsutil0.symbols | ||
license-text-about-dialog | ||
postinst | ||
rules | ||
templates | ||
tshark.docs | ||
tshark.install | ||
tshark.manpages | ||
wireshark-common.config | ||
wireshark-common.install | ||
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.docs | ||
wireshark.install | ||
wireshark.manpages | ||
wireshark.menu |
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