Point to Brimcap that uses new build-zeek artifact #2971
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v6.0.2-brim3 is a new Zeek artifact that's included in the Brimcap v1.6.0-beta1 pre-release artifact pointed at by this branch. I propose merging this PR to allow us to start using the new Zeek in our own internal Zui testing and also encourage community users to start trying it out via Zui Insiders.
Assuming that all goes well, when prepping the next set of GA release, I'll make a GA Brimcap
v1.6.0that points to the same v6.0.2-brim3 Zeek, and Zui can start pointing at that GA Brimcap+Zeek combo.I've made a Zui dev build based off this branch and tested it successfully with multiple pcaps on macOS, Linux, Ubuntu (
.debinstaller) and Rocky (.rpminstaller).