- Advance Zed dependency to include recent fixes/enhancements
- Update bundled Zeek to v7.0.0-brim1 (#353)
- Because Brimcap is dependent on the Zed project, GA Brimcap release major/minor version numbers are now synchronized to the corresponding Zed release
- Advance Zed dependency to include recent fixes/enhancements
- Advance Zed dependency to include recent fixes/enhancements
- Update bundled Zeek to v6.2.0-brim2 (#342)
- Update the Custom Brimcap Configuration wiki article to reflect recent changes in Zed, Zui, Zeek, and
nfdump
(#340)
- Advance Zed dependency to include recent fixes/enhancements
- Update bundled Zeek to v6.2.0-brim1 (#338)
- Switch the
gopacket
dependency to an implementation that supports cooked-mode/SLL link layer protocol (#336)
- Advance Zed dependency to include recent fixes/enhancements
- Update bundled Zeek to v6.0.3-brim1 from new build-zeek repository (#333)
- Fix an issue where errors were incorrectly returned when pcap analyzers successfully exited without having read all input data (#332)
- Advance Zed dependency to include recent fixes/enhancements
- Advance Zed dependency to include a recent fix
- Advance Zed dependency to include recent fixes/enhancements
- Fix an issue where
brimcap -version
output was showing-dirty
(#316) - Advance Zed dependency to include recent fixes/enhancements
- Advance Zed dependency to include recent fixes/enhancements
- The Suricata shaper now places the
event_type
to the left ofts
to improve tile placement in Zui (#308) - Advance Zed dependency to include recent fixes/enhancements
- Update bundled Suricata to v5.0.3-brim5, which fixes zui/2715 (#305)
- Advance Zed dependency to include recent fixes/enhancements
- Update bundled Suricata to allow use of local rules (#272, #274)
brimcap search
: parse-duration
argument as a ZSON duration (#244)brimcap slice
: parse-to
and-from
arguments as an RFC 3339 timestamp (#243)brimcap ts
: print timestamps in RFC 3339 format (#243)- Remove
brimcap migrate
(#234)
- Fix an issue where pcap index entries for legacy Spaces were not being migrated (#156)
- Allow expansion of environment variables in Brimcap config YAML (#153)
- Additions to custom YAML configuration (#148)
- A
root
option can be used to specify the Brimcap root location name
is now a required part of ananalyzer
configuration
- A
- Update legacy Space migration to work with Zed Lake branches (#140, #145)
- Fix an issue where temporary analyzer directories were not being deleted on exit (#137)
- Fix an issue where legacy Space migration would fail for a custom Data Directory in Brim (#133)
- Fix an issue where stale packet index entries could cause a failure to extract a flow from another pcap (#128)
- Include the name of the analyzer process with any warnings & errors it generates (#122)
- Adjust defaults for whether logging during analysis is output as JSON vs. status line (#123)
- Rather than quitting, emit a warning and continue if
brimcap analyze
fails to read an output file (#125)
- Move the Geolocation article over from the Brimcap wiki (#104)
- Refactor
brimcap analyze
to use the new Zed Lake add/commit endpoints and fix a deadlock issue (#110) - Fix a deadlock issue that was caused by an analyze process writing no records (#115)
- Fix the percentage and byte counts on the command line status updates (#116)
- Drop
brimcap load
in favor of granular use ofbrimcap analyze
,brimcap index
andzapi
(#117, #114, #120)
- Publish Custom Brimcap Configuration wiki article (#72)
- Update the README (#96)
- Change
.
tothis
in Suricata shaper (#92) - Fix an issue loading pcaps on some Linux distributions by using new Suricata artifact v5.0.3-brim2 (#100)
- Fix an issue where Space migrations could fail on Windows (#79)
- Generate an error message during abort of Space migration (#86)
- Create a pcap troubleshooting wiki article that includes info formerly from the Brim wiki (#83)
- Add SIGTERM to the list of signals Brimcap listens to for graceful shutdown (#88)
- Keep aborted Spaces so the caller of Brimcap (i.e., the Brim app) can handle cleanup (#89)
- Have Brimcap start using the new Zed Lake client (#90)
- Remove the
brimcap launch
command, since Brim will dobrimcap search
(#56) - Adjust
brimcap load
to use the endpoints inzed lake serve
(#63) - Fix an issue with
pcap_path
not being stored as an absolute path, which caused problems extracting flows (#67) - Add the hidden
brimcap migrate
command which Brim will use for migrating legacy Space data (#66)
- Fix an issue where use of symlinks in the root was preventing
brimcap load
from working on Windows (#39)
- Initial release, still being tested.