Arne Welzel 3f2fe6fc3d control: Use Cluster::publish() for replying ... Switching to ZeroMQ as cluster backend and dabbling with zeekctl and WebSocket, replies didn't arrive due to the usage of Broker::publish() rather than Cluster::publish(). Additionally, add the node name to the topic on which we reply so that the receiver can figure out which node sent the reply. It could've been a separate event parameter, but the topic appears just fine.		2025-07-23 11:59:32 +02:00
..
base	Return weird if a log line is over a configurable size limit	2025-07-21 09:14:52 -07:00
policy	control: Use Cluster::publish() for replying	2025-07-23 11:59:32 +02:00
site	site/local: Switch to detect-sql-injection	2025-05-20 16:24:28 +02:00
spicy	Spicy: Add functions to check if Zeek provides an analyzer of a given name.	2025-07-15 14:22:27 +02:00
zeekygen	Add a VLAN-aware flow tuple implementation.	2025-06-25 13:19:26 +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	Add a VLAN-aware flow tuple implementation.	2025-06-25 13:19:26 +02:00