zeek/scripts
Arne Welzel eef7acc1e9 cluster/main: Remove extra @if ( Cluster::is_enabled() )
These have been discussed in the context of "@if &analyze" [1] and
am much in favor for not disabling/removing ~100 lines (more than
fits on a single terminal) out from the middle of a file. There's no
performance impact for having these handlers enabled unconditionally.
Also, any future work on "@if &analyze" will look at them again which
we could also skip.

This also reverts back to the behavior where the Cluster::LOG stream
is created even in non cluster setups like in previous Zeek versions.
As long as no one writes to it there's essentially no difference. If
someone does write to Cluster::LOG, I'd argue not black holing these
messages is better. Schema generators using Log::active_streams will
continue to discover Cluster::LOG even if they run in non-cluster
mode.

https://github.com/zeek/zeek/pull/3062#discussion_r1200498905
2023-06-06 15:20:10 +02:00
..
base cluster/main: Remove extra @if ( Cluster::is_enabled() ) 2023-06-06 15:20:10 +02:00
policy catch-and-release: Mark cr_check_rule as is_used 2023-05-31 00:37:38 -07:00
site policy: Import zeek-community-id scripts into protocols/conn frameworks/notice 2023-04-24 09:43:19 +02:00
spicy Simplify code generated for Spicy analyzer port ranges. 2023-05-29 12:20:44 +02:00
zeekygen Move spicy/misc scripts to policy and clarify purpose. 2023-05-16 10:21:21 +02:00
CMakeLists.txt Use the same rules as cmake submodule to reformat Zeek 2023-05-09 08:31:43 -07:00
test-all-policy.zeek Move spicy/misc scripts to policy and clarify purpose. 2023-05-16 10:21:21 +02:00