From 2dbcea6bbf5b3d15f261fd581ed6259566de1c64 Mon Sep 17 00:00:00 2001 From: Craig Leres Date: Tue, 22 Aug 2023 13:34:35 -0700 Subject: security/zeek: Update to 6.0.0 https://github.com/zeek/zeek/releases/tag/v6.0.0 This is the latest major version number Long-Term Support (LTS) release of Zeek. The NETMAP option has been removed; it was too difficult to build it without zeek being installed in %%PREFIX%%. The consensus was that this was a rarely used feature, please reach out to me if need this (I've done some work on a new security/zeek-netmap port that is probably the right way forward). When I upgraded zeek on my systems I found some cruft left over from previous versions. The way I recommend upgrading from 5.0.9 to 6.0.0 is: service zeek stop pkg delete -fy zeek py311-zkg [clean up leftover files in /usr/local/lib/zeek] pkg install -y zeek service zeek deploy Changes: - Zeek now treats private address space (i.e., non-routable IP address ranges) as local by default - Telemetry centralization and Prometheus exposition is not enabled by default anymore - Custom source tarballs require a repo-info.json file. - Plugin authors should raise the minimum required CMake version to 3.15 to ensure compatibility with new CMake scaffolding included in this release - Zeek container images are not pushed to the zeekurity organization anymore - The error message returned when using bro_init, bro_done, and bro_script_loaded events is now removed Reported by: Tim Wojtulewicz --- UPDATING | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'UPDATING') diff --git a/UPDATING b/UPDATING index c6c2e3374c5e..59ee7f3b456f 100644 --- a/UPDATING +++ b/UPDATING @@ -5,6 +5,27 @@ they are unavoidable. You should get into the habit of checking this file for changes each time you update your ports collection, before attempting any port upgrades. +20230822: +AUTHOR: leres@FreeBSD.org + + security/zeek has been upgraded to 6.0.0 and the NETMAP option + was removed; it was too difficult to build it without zeek being + installed in %%PREFIX%%. + + The consensus was that this was a rarely used feature, please + reach out to me if need this (I've done some work on a new + security/zeek-netmap port that is probably the right way forward). + + When I upgraded zeek on my systems I found some cruft left over + from previous versions. The way I recommend upgrading from 5.0.9 to + 6.0.0 is: + + service zeek stop + pkg delete -fy zeek py311-zkg + [clean up leftover files in /usr/local/lib/zeek] + pkg install -y zeek + service zeek deploy + 20230817: AFFECTS: users of databases/redis AUTHOR: yasu@FreeBSD.org -- cgit v1.2.3