![]() Create a "registration" system for Follow functionality so most of the work can be abstracted into a dissector and GUI can just be responsible for "display". This also removes the global variables in follow.c to open up multithreading possibilities. TCP, UDP and HTTP all have the same "tap interface" for Follow functionality (passing a tvb with byte data to "follow"). SSL still has it's own behavior, so Follow structures have to take that into account. TShark through the Follow registration now has support for HTTP. The only thing possibly missing is dynamic menu generation to further reduce explicit knowledge of Follow "type" (and rely on registration) Bug: 11988 Change-Id: I559d9ee1312406ad0986d4dce9fa67ea2103b339 Reviewed-on: https://code.wireshark.org/review/13161 Reviewed-by: Michael Mann <mmann78@netscape.net> |
||
---|---|---|
.. | ||
patches | ||
po | ||
source | ||
changelog | ||
compat | ||
control | ||
copyright | ||
dirs | ||
ethereal-common.NEWS | ||
geoip_db_paths | ||
headers-check.c | ||
libwireshark-data.install | ||
libwireshark-dev.install | ||
libwireshark0.install | ||
libwireshark0.symbols | ||
libwiretap-dev.install | ||
libwiretap0.docs | ||
libwiretap0.install | ||
libwiretap0.symbols | ||
libwscodecs0.install | ||
libwscodecs0.symbols | ||
libwsutil-dev.install | ||
libwsutil0.install | ||
libwsutil0.symbols | ||
license-text-about-dialog | ||
postinst | ||
README.Debian | ||
README.Debian.security | ||
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-gtk.docs | ||
wireshark-gtk.install | ||
wireshark-qt.docs | ||
wireshark-qt.install | ||
wireshark-qt.manpages |
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