Johanna Amann 21888a145a SSL: do not try to disable failed analyzer ... Currently, if a TLS/DTLS analyzer fails with a protocol violation, we will still try to remove the analyzer later, which results in the following error message: error: connection does not have analyzer specified to disable Now, instead we don't try removing the analyzer anymore, after a violation occurred.		2023-05-03 11:16:14 +01:00
..
files	Spelling fixes: scripts	2022-11-02 17:36:39 -04:00
frameworks	Merge remote-tracking branch 'origin/topic/awelzel/zeekctl-multiple-loggers'	2023-04-27 12:17:02 +02:00
misc	annotate base scripts with &is_used as needed	2022-05-26 17:39:17 -07:00
packet-protocols	Add forwarding from VLAN analyzer into LLC, SNAP, and Novell 802.3 analyzers	2023-04-25 12:29:55 -07:00
protocols	SSL: do not try to disable failed analyzer	2023-05-03 11:16:14 +01:00
utils	Treat private address space as site-local by default	2023-03-15 17:01:00 -07:00
init-bare.zeek	ip4_hdr: Add DF, MF, offset and sum fields	2023-04-29 17:09:43 +02: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