No description
Find a file
Christian Kreibich e8f0f727cd Fix MMDB code to re-open explicitly opened DBs correctly
The filename from which a DB first gets opened (either via an explicitly
specified filename, or via the path sequence now configurable at the script
layer) is now "sticky", meaning re-opening won't switch to a different file.

This was easiest by moving most state into the MMDB class itself. The previous
approach of tracking the two DB instances via a smart pointer and blowing the
pointed-to objects away as needed is now instead one of two objects fixed over
the lifetime of Zeek, able to open/close/reopen their underlying Maxmind DBs.

The MMDB class now only has one Lookup() method since there was no need to break
them apart -- it saves the return of a MMDB_lookup_result_s over the stack and
there's no need for throwing an exception.
2024-01-10 20:44:40 -08:00
.github/workflows generate-docs: Bump ccache from 500M to 2000M 2023-09-27 18:20:36 +02:00
auxil Bump zeekjs to pick up dprintf warning fix 2024-01-08 13:26:57 -07:00
ci ci/btest: Remove ZEEK_PROFILER_FILE from btest.cfg, set in ci/test.sh explicitly 2023-12-15 15:23:52 +01:00
cmake@01fcb68300 Set -Werror / /WX via target_compile_options to force warnings as errors 2024-01-08 13:25:05 -07:00
cmake_templates zeek-config.h: Drop NEED_KRB5_H 2023-08-28 11:31:05 +02:00
doc@9ab32b867d Update doc submodule [nomail] [skip ci] 2024-01-11 00:12:54 +00:00
docker Add jq to final.Dockerfile 2023-11-21 22:23:37 +09:00
man Use the same rules as cmake submodule to reformat Zeek 2023-05-09 08:31:43 -07:00
scripts Move MaxMind/GeoIP BiF functionality into separate file 2024-01-10 20:28:37 -08:00
src Fix MMDB code to re-open explicitly opened DBs correctly 2024-01-10 20:44:40 -08:00
testing Add btest to verify behavior of re-opened MMDBs opened directly via BIFs 2024-01-10 20:44:40 -08:00
.cirrus.yml CI: Remove unused openssl30_config 2024-01-08 13:26:57 -07:00
.clang-format Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.clang-tidy Disable annoying bugprone-easily-swappable-parameters clang-tidy check [skip ci] 2022-10-07 16:15:47 -07:00
.cmake-format.json Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.dockerignore Add .dockerignore to suppress btest artifacts 2021-09-24 17:04:26 -07:00
.git-blame-ignore-revs Update .git-blame-ignore-revs 2023-10-30 09:42:39 +01:00
.gitattributes GH-1497: Support CRLF line-endings in Zeek scripts and signature files 2021-04-08 20:32:30 -07:00
.gitignore Cirrus configuration for Windows builds 2022-11-09 18:16:13 +02:00
.gitmodules Move Spicy submodule a layer up. 2023-05-16 12:09:12 +02:00
.pre-commit-config.yaml Format JSON with clang-format 2023-10-30 09:41:13 +01:00
.style.yapf Format Python scripts with yapf. 2021-11-24 23:13:24 +01:00
.typos.toml retention of superseded AST elements to prevent pointer mis-aliasing 2023-11-10 11:06:16 +01:00
.update-changes.cfg Add script to update external test repo commit pointers 2019-04-05 17:09:01 -07:00
CHANGES Merge branch 'topic/timw/move-bifs' 2024-01-10 12:32:58 -07:00
CMakeLists.txt Set -Werror / /WX via target_compile_options to force warnings as errors 2024-01-08 13:25:05 -07:00
configure Set -Werror / /WX via target_compile_options to force warnings as errors 2024-01-08 13:25:05 -07:00
COPYING Update COPYING to 2023 2023-01-03 12:10:03 -07:00
COPYING-3rdparty Rename COPYING.3rdparty to COPYING-3rdparty 2023-01-03 12:10:03 -07:00
INSTALL Update documentation to include "Book of Zeek" revisions 2021-02-01 15:54:36 -08:00
Makefile Fix usage of realpath on macOS, instead preferring grealpath 2023-06-13 15:51:47 -07:00
NEWS Merge remote-tracking branch 'origin/topic/awelzel/quic-draft-mvfst-versions' 2024-01-10 14:08:01 +01:00
README Add tooling section to README 2023-01-27 13:03:52 -07:00
README.md Update link to slack in README.md 2023-06-01 14:21:44 +02:00
VERSION Merge branch 'topic/timw/move-bifs' 2024-01-10 12:32:58 -07:00
zeek-path-dev.in Move CMake template files to separate directory 2023-06-26 13:39:59 -07:00

Zeek Logo

The Zeek Network Security Monitor

A powerful framework for network traffic analysis and security monitoring.

Key FeaturesDocumentationGetting StartedDevelopmentLicense

Follow us on Twitter at @zeekurity.

Coverage Status Build Status

Slack Discourse

Key Features

  • In-depth Analysis Zeek ships with analyzers for many protocols, enabling high-level semantic analysis at the application layer.

  • Adaptable and Flexible Zeek's domain-specific scripting language enables site-specific monitoring policies and means that it is not restricted to any particular detection approach.

  • Efficient Zeek targets high-performance networks and is used operationally at a variety of large sites.

  • Highly Stateful Zeek keeps extensive application-layer state about the network it monitors and provides a high-level archive of a network's activity.

Getting Started

The best place to find information about getting started with Zeek is our web site www.zeek.org, specifically the documentation section there. On the web site you can also find downloads for stable releases, tutorials on getting Zeek set up, and many other useful resources.

You can find release notes in NEWS, and a complete record of all changes in CHANGES.

To work with the most recent code from the development branch of Zeek, clone the master git repository:

git clone --recursive https://github.com/zeek/zeek

With all dependencies in place, build and install:

./configure && make && sudo make install

Write your first Zeek script:

# File "hello.zeek"

event zeek_init()
    {
    print "Hello World!";
    }

And run it:

zeek hello.zeek

For learning more about the Zeek scripting language, try.zeek.org is a great resource.

Development

Zeek is developed on GitHub by its community. We welcome contributions. Working on an open source project like Zeek can be an incredibly rewarding experience and, packet by packet, makes the Internet a little safer. Today, as a result of countless contributions, Zeek is used operationally around the world by major companies and educational and scientific institutions alike for securing their cyber infrastructure.

If you're interested in getting involved, we collect feature requests and issues on GitHub here and you might find these to be a good place to get started. More information on Zeek's development can be found here, and information about its community and mailing lists (which are fairly active) can be found here.

License

Zeek comes with a BSD license, allowing for free use with virtually no restrictions. You can find it here.

Tooling

We use the following tooling to help discover issues to fix, amongst a number of others.