Robin Sommer bc252c63dc Add BIF have_spicy_analyzers(). ... We previously used the Spicy plugin's `Spicy::available` to test for Spicy support. However, having Spicy support does not necessarily mean that we have built Zeek with its in-tree Spicy analyzers: the Spicy plugin could have been pulled in from external. The new BIF now reliably tells us whether the Spicy analyzers are available; its result corresponds to what `zeek-config --have-spicy-analyzers` returns as well. We also move the two current checks over to use this BIF. (Note: I refrained from renaming the CMake-side `USE_SPICY_ANALYERS` to `HAVE_SPICY_ANALYZERS`. We should do this eventually for consistency, but I didn't want to make more changes than necessary right now.)		2023-02-03 13:47:26 +01:00
..
files	Spelling fixes: scripts	2022-11-02 17:36:39 -04:00
frameworks	broker/store: Extend SQLiteOptions around data safety and performance	2023-01-30 10:25:37 +01:00
misc	annotate base scripts with &is_used as needed	2022-05-26 17:39:17 -07:00
packet-protocols	gtpv1: Do not register for protocol detection	2022-08-26 10:47:38 +02:00
protocols	Add BIF have_spicy_analyzers().	2023-02-03 13:47:26 +01:00
utils	Spelling fixes: scripts	2022-11-02 17:36:39 -04:00
init-bare.zeek	Merge remote-tracking branch 'security/topic/timw/131-smb-fscontrol-overflow'	2023-02-01 10:48:16 -07:00
init-default.zeek	Provide infrastructure to migrate legacy analyzers to Spicy.	2023-02-01 11:33:48 +01:00
init-frameworks-and-bifs.zeek	analyzer: Add analyzer.log for logging violations/confirmations	2023-01-09 18:11:49 +01:00
init-supervisor.zeek	Establish a separate init script when using the supervisor	2021-07-08 13:12:53 -07:00