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
..
analyzer	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
cluster	cluster/telemetry: Move topic_normalization redef to zeromq	2025-06-26 15:22:11 +02:00
conn_key	ip/vlan_fivetuple: Populate nested conn_id_context, not conn_id	2025-07-03 18:19:46 +02:00
control	control: Use Cluster::publish() for replying	2025-07-23 11:59:32 +02:00
dpd	Move detect-protocol from frameworks/dpd to frameworks/analyzer	2025-06-04 12:16:09 +01:00
files	Remove full scripts marked as 6.1 deprecations	2023-06-14 10:07:22 -07:00
intel	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
management	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
netcontrol	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
notice	policy/community-id: Populate conn$community_id in new_connection()	2024-11-08 18:19:55 +01:00
packet-filter	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
signatures	signatures/iso-9660: Add \x01 suffix to CD001	2024-02-26 21:00:01 +01:00
software	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00
spicy	all: Fix typos identified by typos pre-commit hook	2023-06-13 17:57:32 +02:00
storage/backend	Add busy_timeout script-level option, override any busy_timeout pragma	2025-06-05 10:21:50 -07:00
telemetry	Prefer explicit construction to coercion in record initialization	2025-07-11 16:28:37 -07:00