forked from osmocom/wireshark
537b083e02
Adjust the following CMake and Autotools behaviors in order to synchronize their respective install behaviors: - Disable tfshark by default in CMakeOptions.txt - Add profiles/Bluetooth/preferences to Makefile.am - Add missing captype and ciscodump entries to doc/Makefile.am - Install help/faq.txt on all platforms in CMakeLists.txt - Add BUILD_corbaidl2wrs, BUILD_dcerpcidl2wrs, and BUILD_xxx2deb options to CMake and use them to adjust the corresponding parts of the build. - Pull the DCERPC idl2wrs build steps into the top-level CMakeLists.txt. This change doesn't sync everything. Some installed content still diverges, including the following: - CMake installs a bunch of modules into lib/wireshark: FindGLIB2.cmake FindWireshark.cmake FindWSWinLibs.cmake LocatePythonModule.cmake UseAsn2Wrs.cmake UseMakeDissectorReg.cmake WiresharkConfig.cmake WiresharkConfigVersion.cmake Do we need any or all of these? If so, should the Autotools behavior be synced accordingly? - Autotools installs libtool .la files. It also installs wireshark-gtk.desktop unconditionally. Change-Id: I7846efe08f7139c31b6ceca6f08a1fa5168b3e22 Reviewed-on: https://code.wireshark.org/review/23041 Reviewed-by: Gerald Combs <gerald@wireshark.org> Petri-Dish: Gerald Combs <gerald@wireshark.org> Tested-by: Petri Dish Buildbot <buildbot-no-reply@wireshark.org> Reviewed-by: Michael Mann <mmann78@netscape.net> |
||
---|---|---|
.. | ||
patches | ||
po | ||
source | ||
README.Debian | ||
README.Debian.security | ||
changelog | ||
compat | ||
control | ||
copyright | ||
dirs | ||
ethereal-common.NEWS | ||
geoip_db_paths | ||
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 | ||
libwscodecs0.install | ||
libwscodecs0.symbols | ||
libwsutil-dev.install | ||
libwsutil0.install | ||
libwsutil0.symbols | ||
license-text-about-dialog | ||
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-gtk.docs | ||
wireshark-gtk.install | ||
wireshark-gtk.lintian-overrides | ||
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