Arne Welzel bc8fd5a4c6 Introduce generic analyzer_confirmation_info and analyzer_violation_info ... Introduce two new events for analyzer confirmation and analyzer violation reporting. The current analyzer_confirmation and analyzer_violation events assume connection objects and analyzer ids are available which is not always the case. We're already passing aid=0 for packet analyzers and there's not currently a way to report violations from file analyzers using analyzer_violation, for example. These new events use an extensible Info record approach so that additional (optional) information can be added later without changing the signature. It would allow for per analyzer extensions to the info records to pass analyzer specific info to script land. It's not clear that this would be a good idea, however. The previous analyzer_confirmation and analyzer_violation events continue to exist, but are deprecated and will be removed with Zeek 6.1.		2022-09-27 17:49:51 +02:00
..
control	Remove trailing whitespace from script files	2021-10-20 09:57:09 -07:00
dpd	Introduce generic analyzer_confirmation_info and analyzer_violation_info	2022-09-27 17:49:51 +02:00
files	files.log: Unroll and introduce uid and id fields	2022-08-16 17:22:20 +02:00
intel	Fix host header normalization in intel framework.	2021-12-21 21:54:47 +01:00
management	Update Management framework to new Supervisor::NodeConfig script fields	2022-09-02 12:12:19 -07:00
netcontrol	Support for log filter policy hooks	2020-09-30 12:32:45 -07:00
notice	update uses of "when" in base scripts to include captures	2022-01-07 14:53:33 -08:00
packet-filter	More bro-to-zeek renaming in scripts and other files	2019-05-16 02:36:41 -05:00
signatures	Hopefully the last major script reorganization.	2011-08-05 23:09:53 -04:00
software	policy: Use literal dots for patterns used against content-type and hostname	2022-07-11 10:34:47 +02:00
telemetry	Introduce telemetry framework	2022-08-05 11:43:44 +02:00