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
..
files	GH-1634: Address feedback	2021-07-02 15:12:58 +01:00
frameworks	Introduce generic analyzer_confirmation_info and analyzer_violation_info	2022-09-27 17:49:51 +02: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	Introduce generic analyzer_confirmation_info and analyzer_violation_info	2022-09-27 17:49:51 +02:00
utils	strings: Implement join_string_set() as bif	2022-09-20 23:07:26 +02:00
init-bare.zeek	Introduce generic analyzer_confirmation_info and analyzer_violation_info	2022-09-27 17:49:51 +02:00
init-default.zeek	frameworks/dpd: Move to frameworks/analyzer/dpd, load by default	2022-08-31 16:50:47 +02:00
init-frameworks-and-bifs.zeek	GH-1122: Allow initializing globals with calls to subdir BIFs	2020-08-27 12:20:37 -07:00
init-supervisor.zeek	Establish a separate init script when using the supervisor	2021-07-08 13:12:53 -07:00