security/zeek: revert b6a8929a2551 for pkg-plist
I get package errors with that version (for 13.2/amd64 at least):
=======================<phase: package >============================
===> Building package for zeek-6.0.0
pkg-static: Unable to access file /wrkdirs/usr/ports/security/zeek/work/stage/usr/local/include/zeek/analyzer/protocol/finger/legacy/events.bif.h:No such file or directory
pkg-static: Unable to access file /wrkdirs/usr/ports/security/zeek/work/stage/usr/local/include/zeek/analyzer/protocol/syslog/legacy/events.bif.h:No such file or directory
pkg-static: Unable to access file /wrkdirs/usr/ports/security/zeek/work/stage/usr/local/share/zeek/base/bif/plugins/Zeek_Finger.events.bif.zeek:No such file or directory
pkg-static: Unable to access file /wrkdirs/usr/ports/security/zeek/work/stage/usr/local/share/zeek/base/bif/plugins/Zeek_Syslog.events.bif.zeek:No such file or directory
*** Error code 1
Maybe it's an options thing? I have everything set except PERFTOOLS
and BUILD_TYPE set to RELEASE.
While here update LICENSE.
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
security/zeek: Update to 5.0.9
https://github.com/zeek/zeek/releases/tag/v5.0.9
This release fixes the following potential DoS vulnerabilities:
- A specially-crafted series of FTP packets with a CMD command
with a large path followed by a very large number of replies
could cause Zeek to spend a long time processing the data.
- A specially-crafted with a truncated header can cause Zeek to
overflow memory and potentially crash.
- A specially-crafted series of SMTP packets can cause Zeek to
generate a very large number of events and take a long time to
process them.
- A specially-crafted series of POP3 packets containing MIME data
can cause Zeek to spend a long time dealing with each individual
file ID.
This release fixes the following bug:
- This release includes a fixes to Zeek and updates to the Broker
and Spicy submodules to support building against GCC 13.
Reported by: Tim Wojtulewicz
Security: 1ab7357f-a3c2-406a-89fb-fd00e49a71b5
security/zeek: Update to 5.0.8
https://github.com/zeek/zeek/releases/tag/v5.0.8
This release fixes the following potential DoS vulnerabilities:
- A specially-crafted stream of FTP packets containing a command
reply with many intermediate lines can cause Zeek to spend a
large amount of time processing data.
- A specially-crafted set of packets containing extremely large
file offsets cause cause the reassembler code to allocate large
amounts of memory.
- The DNS manager does not correctly expire responses that don't
contain any data, such those containing NXDOMAIN or NODATA status
codes. This can lead to Zeek allocating large amounts of memory
for these responses and never deallocating them.
- A specially-crafted stream of RDP packets can cause Zeek to spend
large protocol validation.
- A specially-crafted stream of SMTP packets can cause Zeek to
spend large amounts of time processing data.
This release fixes the following bugs:
- Data stores used by the known-{hosts,certs,services} policies
now default to using local stores instead of Broker stores.
- The VXLAN and Geneve report analyzer confirmations once their
protocols have been fully parsed, but before attempting to forward
to the tunneled packets to other analyzers.
- New wierds were added to the AYIYA, Geneve, and VXLAN analyzers
(ayiya_empty_packet, geneve_empty_packet, and vxlan_empty_packet).
- A new script-level option Pcap::non_fd_timeout was added to allow
fine-tuning the amount of time to sleep on each IO loop when
using a packet source that doesn't provide a file descriptor
(e.g. Myricom).
- Avoid attempting to retrieve packets during every loop for a
packet source, instead switching to a predictive approach that
keeps track of whether or not that packet source has previously
seen traffic.
Reported by: Tim Wojtulewicz
Security: 96d6809a-81df-46d4-87ed-2f78c79f06b1
security/zeek: Update to 5.0.7
https://github.com/zeek/zeek/releases/tag/v5.0.7
This release fixes the following potential DoS vulnerabilities:
- Receiving DNS responses from async DNS requests (via the
lookup_addr, etc BIF methods) with the TTL set to zero could
cause the DNS manager to eventually stop being able to make new
requests.
- Specially-crafted FTP packets with excessively long usernames,
passwords, or other fields could cause log writes to use large
amounts of disk space.
- The find_all and find_all_ordered BIF methods could take extremely
large amounts of time to process incoming data depending on the
size of the input.
This release fixes the following bugs:
- Various issues with signed/unsigned character discrepancies on
arm64 builds are fixed.
- A performance degredation in debug builds involving hashing large
keys for Dictionaries was fixed.
Reported by: Tim Wojtulewicz
Security: 7a425536-74f7-4ce4-9768-0079a9d44d11
security/zeek: Update to 5.0.6
https://github.com/zeek/zeek/releases/tag/v5.0.6
This release fixes the following potential DoS vulnerabilities:
- A missing field in the SMB FSControl script-land record could
cause a heap buffer overflow when receiving packets containing
those header types.
- Receiving a series of packets that start with HTTP/1.0 and then
switch to HTTP/0.9 could cause Zeek to spend a large amount of
time processing the packets.
- Receiving large numbers of FTP commands sequentially from the
network with bad data in them could cause Zeek to spend a large
amount of time processing the packets, and generate a large
amount of events.
This release fixes the following bugs:
- Zeek could throw a scripting error when receiving SMB1 packets
containing connect_andx_response messages prior to receiving an
associated request.
- A performance regression from 4.2 to 5.0 when reading pcap files
related to Broker's internal clock was fixed.
- Notices created for files transferred over multiple connections
will now be associated with one of the connections rather than
none.
- A new file_over_new_connection event was added to the Intel
framework, for use when receiving files over established connections
(for example, HTTP).
- The error message returned when trying use invalid enums in
scripts now correctly includes the script location.
Reported by: Tim Wojtulewicz
Security: 2b5fc9c4-eaca-46e0-83d0-9b10c51c4b1b
security/zeek: Update to 5.0.5
https://github.com/zeek/zeek/releases/tag/v5.0.5
This release fixes the following bugs:
- Update broker to version 2.3.6. This broker release fixes some
failures when building against Python 3.11 and above.
Reported by: Tim Wojtulewicz
security/zeek: Update to 5.0.4
https://github.com/zeek/zeek/releases/tag/v5.0.4
This release fixes the following potential DoS vulnerabilities:
- A specially-crafted series of HTTP 0.9 packets can cause Zeek
to spend large amounts of time processing the packets.
- A specially-crafted FTP packet can cause Zeek to spend large
amounts of time processing the command.
- A specially-crafted IPv6 packet can cause Zeek to overflow memory
and potentially crash.
This release fixes the following bugs:
- Fix a potential stall in Broker’s internal data pipeline.
Reported by: Tim Wojtulewicz
Security: ???
security/zeek: Update to 5.0.3
https://github.com/zeek/zeek/releases/tag/v5.0.3
This release fixes the following potential DoS vulnerabilities:
- Fix an issue where a specially-crafted FTP packet can cause Zeek
to spend large amounts of time attempting to search for valid
commands in the data stream.
- Fix a possible overflow in the Zeek dictionary code that may
lead to a memory leak.
- Fix an issue where a specially-crafted packet can cause Zeek to
spend large amounts of time reporting analyzer violations.
- Fix a possible assert and crash in the HTTP analyzer when receiving
a specially-crafted packet.
- Fix an issue where a specially-crafted HTTP or SMTP packet can
cause Zeek to spend a large amount of time attempting to search
for filenames within the packet data.
- Fix two separate possible crashes when converting processed IP
headers for logging via the raw_packet event handlers.
This release fixes the following bugs:
- Fix a possible crash with when statements where lambda captures
of local variables sometimes overflowed the frame counter.
- Reduced the amount of analyzer_confirmation events that are
raised for packets that contain tunnels.
- Fix a long-standing bug where TCP reassembly would not function
correctly for some analyzers if dpd_reassemble_first_packets was
set to false.
- Fix a performance bug in the Zeek dictionary code in certain
cases, such as copying a large number of entries from one
dictionary into another.
- Fix a performance issue when inserting large numbers of elements
into a Broker store when Broker::scheduler_policy is set to
stealing.
- Fix a Broker performance issue when distributing large amounts
of data from the input framework to proxies/workers at startup.
- Fix an issue with messaging between proxies and workers that
resulted in error messages being reported.
- Updated the list of DNS type strings to reflect the correct.
Reported by: Tim Wojtulewicz
Security: 60d4d31a-a573-41bd-8c1e-5af7513c1ee9
security/zeek: Update to 5.0.2
https://github.com/zeek/zeek/releases/tag/v5.0.2
Security fixes:
- Fix a possible overflow and crash in the ICMP analyzer when
receiving a specially crafted packet
- Fix a possible overflow and crash in the IRC analyzer when
receiving a specially crafted packet
- Fix a possible overflow and crash in the SMB analyzer when
receiving a specially crafted packet
- Fix two possible crashes when converting IP headers for output
via the raw_packet event
Other changes:
- Fix a bug that prevented Broker nodes to recover from OpenSSL errors.
- Fix handling of buffer sizes that caused Broker to stall despite
having sufficient capacity.
- Fix an issue with signal handling that could prevent Zeek from
exiting via ctrl-c when reading scripts from stdin.
Also fix new PR 266345 issue reported by @pkubaj ("fails to build
without SPICY enabled").
PR: 266345
Reported by: Tim Wojtulewicz, pkubaj
security/zeek: Port improvements
- Remove useless BROKER option.
- Remove USES=ninja (now implied by USES=cmake).
- Make bison, flex, and swig hard dependencies.
- Strip several installed binaries.
- Remove some test files and directories mistakenly installed by
spicy.
- While we're here, run portfmt.
Thanks to @diizzy for the bulk of these changes.
PR: 266345
Reported by: diizzy
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
This commit implements such a proposal and moves one of the WWW: entries
of each pkg-descr file into the respective port's Makefile. A heuristic
attempts to identify the most relevant URL in case there is more than
one WWW: entry in some pkg-descr file. URLs that are not moved into the
Makefile are prefixed with "See also:" instead of "WWW:" in the pkg-descr
files in order to preserve them.
There are 1256 ports that had no WWW: entries in pkg-descr files. These
ports will not be touched in this commit.
The portlint port has been adjusted to expect a WWW entry in each port
Makefile, and to flag any remaining "WWW:" lines in pkg-descr files as
deprecated.
Approved by: portmgr (tcberner)
security/zeek: Update to 5.0.1
https://github.com/zeek/zeek/releases/tag/v5.0.1
Security fixes since 5.0.0:
- Fix a possible overflow and crash in the ARP analyzer when
receiving a specially crafted packet.
- Fix a possible overflow and crash in the Modbus analyzer when
receiving a specially crafted packet.
- Fix two possible crashes when converting IP headers for output
via the raw_packet event.
- Fix an abort related to an error related to the ordering of
record fields when processing DNS EDNS headers via events
Other changes:
- Fix a number of typos in the weak-keys.zeek script in the SSL
framework.
- Fix build of internal Spicy when using the --disable-cpp-tests
configure flag.
- Avoid calling safe_realloc unnecessarily from ODesc::Grow(),
providing a peformance improvement in some cases.
- Remove use of fallible get_conn_transport_proto() in analyzer_violation
event handlers.
- Remove a warning when receiving packets with invalid or unknown
IP protocol types, preventing it from spamming reporter.log.
- Fix workers failing to peer with proxies if they take too long
to start.
- Fix Zeek build failures when building against an external version
of Spicy.
- Update Spicy to version 1.5.1 and spicy-plugin to 1.3.17.
Reported by: Tim Wojtulewicz
security/zeek: fix build on non aarch64 / amd64 / armv? / i386
1. Enable SPICY only on aarch64 / amd64 / armv? / i386 as specified in
https://github.com/zeek/spicy/blob/d0bc60537b53c3a951a0bdcb7b1c080bbb068abf/hilti/runtime/src/fiber.cc#L252
2. Correct a parameter passed to CMake to disable Spicy.
3. Correct pkg-plist for build with disabled Spicy.
Approved by: portmgr (blanket)
security/zeek: Update input framework patch
https://github.com/zeek/zeek/pull/2266
This version of the patch fixes tail -F semantics when want_record=F.
security/zeek: Patch to allow building without ENABLE_ZEEK_UNIT_TESTS
5.0.0 does not build without ENABLE_ZEEK_UNIT_TESTS enabled.
Apply upstream patch which solves this:
https://github.com/zeek/zeek/pull/2256
Obtained from: Benjamin Bannier
security/zeek: Update to 5.0.0 (latest LTS release)
https://github.com/zeek/zeek/releases/tag/v5.0.0
Changes incompatiable with 4.0.7:
- The script-land ``union`` and ``timer`` types have been removed.
They haven't had any actual semantics backing them for some time
and shouldn't have functioned in any useable way. We opted to
skip the deprecation cycle for these types for that reason.
- Broker now uses a new network backend with a custom network
protocol that is incompatible with the pre-5.0 backend. In
practice, this means Zeek 4.x will not be able to exchange events
with Zeek 5.x. Going forward, this new backend will allow us to
keep the Broker protocol more stable and add new capabilities
in a backwards compatible way.
While we're here add a comment explaining why we really need uname
-p instead of using ARCH (uname -m). Also solve a portlint nag.
Reported by: Tim Wojtulewicz
security/zeek: Patch to provide tail -F semantics for input framework MODE_STREAM
This is a backport of this github pull request:
https://github.com/zeek/zeek/pull/2097
security/zeek: Update to 4.0.7
https://github.com/zeek/zeek/releases/tag/v4.0.7
Security fixes since 4.0.6:
- Fix potential hang in the DNS analyzer when receiving a
specially-crafted packet. Due to the possibility of this happening
with packets received from the network, this is a potential DoS
vulnerability.
Other changes:
- Fix issue with broken libpcaps that return repeat packets, most
notably the version provided with Myricom hardware.
Reported by: Tim Wojtulewicz
security/zeek: Update to 4.0.6
https://github.com/zeek/zeek/releases/tag/v4.0.6
Security fixes since 4.0.5:
- Fix potential unbounded state growth in the FTP analyzer when
receiving a specially-crafted stream of commands. This may lead
to a buffer overflow and cause Zeek to crash. Due to the possibility
of this happening with packets received from the network, this
is a potential DoS vulnerabilty.
Other changes:
- Empty table constructors with &default attributes may cause a
crash.
- Fix a bug in ZAM when a function containing a loop is inlined
- Fix a number of bugs with robust dictionary iteration.
- Fix missing "Reporter" entries when reporting hooks via zeek.
Reported by: Tim Wojtulewicz
security/zeek: Update to 4.0.5
Changes since 4.0.4:
- The highwayhash module was updated to fix a build failure on
FreeBSD.
- A number of fixes for various problems on the CI infrastructure.
- Writers were not being cleaned up correctly when recreating log
streams with the same ID as an existing stream. This could lead
to a crash.
- IP packets with bad/incorrect IP header lengths were not reporting
weirds as they should be.
Reported by: Tim Wojtulewicz
security/zeek: Update to 4.0.4
https://github.com/zeek/zeek/releases/tag/v4.0.4
This release fixes two vulnerabilities:
- Paths from log stream make it into system() unchecked, potentially
leading to commands being run on the system unintentionally.
This requires either bad scripting or a malicious package to be
installed, and is considered low severity.
- Fix potential unbounded state growth in the PIA analyzer when
receiving a connection with either a large number of zero-length
packets, or one which continues ack-ing unseen segments. It is
possible to run Zeek out of memory in these instances and cause
it to crash. Due to the possibility of this happening with packets
received from the network, this is a potential DoS vulnerability.
Other fixes:
- The highwayhash submodule was updated to fix a build failure on
FreeBSD 14.
- Packet sources that don't have a selectable file descriptor could
potentially prevent the network time from ever updating, which
would have adverse effects on the primary run loop such as
preventing timers from executing.
- Specific conditions in the run loop could lead RotationTimers
to get into an infinite loop.
- Specially crafted HTTP packets could avoid the HTTP analyzer.
- Zeekctl crashes using the zeekctl status command if the
StatusCmdShowAll option is set to 1 in zeekctl.cfg.
- The ignore_checksum_nets option does not work correctly if
configured with multiple subnets.
Reported by: Tim Wojtulewicz
Security: d4d21998-bdc4-4a09-9849-2898d9b41459
security/zeek: Add @sample for local.zeek
This github issue:
https://github.com/zeek/zeekctl/issues/35
complained about the lack of a local.zeek file on a fresh install;
adding @sample for local.zeek solves this.
Reported by: shadonet
security/zeek: fix build on powerpc64*
In file included from /wrkdirs/usr/ports/security/zeek/work/zeek-4.0.3/auxil/highwayhash/highwayhash/arch_specific.cc:27:
/usr/include/sys/sysctl.h:1185:25: error: unknown type name 'u_int'
int sysctl(const int *, u_int, void *, size_t *, const void *, size_t);
security/zeek: Unbreak build under 14.0-CURRENT
According to the cpuset(2) man page, sys/param.h must be included
before sys/cpuset.h. This was fixed in zeek (in the highwayhash
submodule) in May of 2020 and undone in August of 2020. Add a patch
that matches the pull request I just created with upstream:
https://github.com/zeek/highwayhash/pull/1
Thanks to @pluknet for diagnosing the build failure.
Reported by: pkg-fallout
security/zeek: Update to 4.0.3
https://github.com/zeek/zeek/releases/tag/v4.0.3
This release fixes the following bugs:
- Zeek now accepts unset fields in the input data only when the
corresponding record field is &optional.
- The version field in ssh.log is now optional and will not be set
if we cannot determine the version that was negotiated by the
client and server.
- Zeekctl could crash at startup on certain compilers and platforms
due to a memory corruption issue in the Broker python bindings.
- The highwayhash submodule was updated to fix a build failure on
FreeBSD for PowerPC.
This release deprecates the following functionality:
- The stepping-stone analyzer is marked as deprecated. It was
partially marked as deprecated in 2.0, and will be fully removed
in v4.1.
Reported by: Tim Wojtulewicz
security/zeek: Update to 4.0.2
https://github.com/zeek/zeek/releases/tag/v4.0.2
This release fixes several potential DoS vulnerabilities:
- Fix potential Undefined Behavior in decode_netbios_name() and
decode_netbios_name_type() BIFs. The latter has a possibility
of a remote heap-buffer-overread, making this a potential DoS
vulnerability.
- Add some extra length checking when parsing mobile ipv6 packets.
Due to the possibility of reading invalid headers from remote
sources, this is a potential DoS vulnerability.
Other fixes:
- Fix heap-use-after-free after clear_table() on a table that uses
expiration attributes.
- Add fatal error for if table/Dictionary state ever becomes invalid
since the behavior becomes unexpected/unclear at that point (e.g.
when table bucket positions become large enough to overflow their
16-bit storage due to aggressive expiration-check settings
preventing the re-positioning items)
- Add missing "zeek/" to header includes, which can prevent external
plugins from compiling against Zeek source-tree (e.g. via
./configure --zeek-dist=)
- Fix reading empty set[enum] values and any vector of enum values
from config files
- Fix type-checks related to list-type equality
Reported by: Tim Wojtulewicz
MFH: 2021Q2
Security: a550d62c-f78d-4407-97d9-93876b6741b9
security/zeek: Add fine grained DEBUG options
Allow the user to pick from DEBUG, MINSIZEREL, RELEASE, and
RELWITHDEBINFO options instead of just DEBUG. Don't STRIP with DEBUG
or RELWITHDEBINFO. Make some minor whitespace changes suggested by
portfmt.
security/zeek: Update to 4.0.1 to fix null-pointer dereference and potential DOS
https://github.com/zeek/zeek/releases/tag/v4.0.1
This release fixes the following vulnerability:
- Fix null-pointer dereference when encountering an invalid enum
name in a config/input file that tries to read it into a set[enum].
For those that have such an input feed whose contents may come
from external/remote sources, this is a potential DoS vulnerability.
Other fixes:
- Fix mime type detection bug in IRC/FTP file_transferred event
for file data containing null-bytes
- Fix potential for missing timestamps in SMB logs
- Remove use of LeakSanitizer API on FreeBSD where it's unsupported
- Fix incorrect parsing of ERSPAN Type I
- Fix incorrect/overflowed n value for SSL_Heartbeat_Many_Requests
notices where number of server heartbeats is greater than number
of client heartbeats.
- Fix missing user_agent existence check in smtp/software.zeek
(causes reporter.log error noise, but no functional difference)
- Fix include order of bundled headers to avoid conflicts with
pre-existing/system-wide installs
- Fix musl build (e.g. Void, Alpine, etc.)
- Fix build with -DENABLE_MOBILE_IPV6 / ./configure --enable-mobile-ipv6
- Add check for null packet data in pcap IOSource, which is an
observed state in Myricom libpcap that crashes Zeek via null-pointer
dereference
- Allow CRLF line-endings in Zeek scripts and signature files
- Fix armv7 build
- Fix unserialization of set[function], generally now used by
connection record removal hooks, and specifically breaking
intel.log of Zeek clusters
- Fix indexing of set/table types with a vector
- Fix precision loss in ASCII logging/printing of large double,
time, or interval values
- Improve handling of invalid SIP data before requests
- Fix copy()/cloning vectors that have holes (indices w/ null
values)
Reported by: Jon Siwek
security/zeek: Unbreak armv7 build and fix testport issue
Add a patch from upstream to fix building on armv7 (used by pfsense):
https://github.com/zeek/zeek/issues/1496
Thanks to @garga for the pointer.
Fix a testport "left over" file @adridg reported. When zeek is run
as part of package installation, it copies some config files to
spool/installed-scripts-do-not-touch/site and local.zeek.sample
hitches a ride and needs to be removed on uninstall. But it is not
really a @sample candidate.
While we're here fix some minor portlint (env -> ${SETENV}) and
clean up some commented out directives.
Reported by: garga adridg
security/zeek: fix build on powerpc64 elfv2
-mpowerp8-vector is now necessary due to use of highwayhash.
Fix typo on sysctlbyname.
Also correct typo in BROKEN entries.
security/zeek: Update to 4.0.0
This is the next Long-Term Support (LTS) major version:
https://github.com/zeek/zeek/releases/tag/v4.0.0
https://zeek.org/2020/12/15/zeek-4-0-release-candidate/
Support for the previous LTS (3.0.x) will end in about two months.
Reported by: Jon Siwek
security/zeek: Update to 3.0.13
https://github.com/zeek/zeek/releases/tag/v3.0.13
This release fixes the following vulnerability:
- Fix ASCII Input reader's treatment of input files containing
null-bytes. An input file containing null-bytes could lead to a
buffer-over-read, crash Zeek, and be exploited to cause Denial
of Service.
And fixes the following bugs:
- MIME sub-entities overwrote top-level header values cause
misleading SMTP log
- Fix incorrect major_subsys_version field in pe_optional_header
event
Reported by: Jon Siwek
security/zeek: Install cmake files
Unstream requested that share/zeek/cmake/* be installed as the files
are used to build zeek plugins.
While here update some pkg-plist @preunexec entries (*.bro -> *.zeek).
Reported by: Robin Sommer, Benjamin Bannier
security/zeek: Improve the pkg upgrade experience
Don't remove %%PREFIX%%/spool/state.db otherwise when zeek is
upgraded zeekctl doesn't detect the running instance and "restart"
fails.
Split uninstall related info in pkg-message.in to a new remove
section (and fix some typos).