zeek/scripts
Johanna Amann 58613f0313 Introduce new c$failed_analyzers field
This field is used internally to trace which analyzers already had a
violation. This is mostly used to prevent duplicate logging.

In the past, c$service_violation was used for a similar purpose -
however it has slightly different semantics. Where c$failed_analyzers
tracks analyzers that were removed due to a violation,
c$service_violation tracks violations - and doesn't care if an analyzer
was actually removed due to it.
2025-06-04 12:07:13 +01:00
..
base Introduce new c$failed_analyzers field 2025-06-04 12:07:13 +01:00
policy Introduce new c$failed_analyzers field 2025-06-04 12:07:13 +01:00
site site/local: Switch to detect-sql-injection 2025-05-20 16:24:28 +02:00
spicy Spicy: Document lifetime semantics of Zeek analyzers created from Spicy. 2025-04-10 12:17:05 +02:00
zeekygen dpd->analyzer.log change - rename files 2025-06-03 16:32:52 +01: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 dpd->analyzer.log change - rename files 2025-06-03 16:32:52 +01:00