You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bugSomething isn't workingcarvingRelating to carving (extraction) of files from traffic and the scanning of those filessensorFor issues dealing with the Hedgehog OS capture sensorzeekRelating to Malcolm's use of Zeek
This morning I discovered an issue where the zeek_carve_logger.py script (which logs hits for files scanned by zeek into signatures(_carved).log). This script would end up creating the $ZEEK_LOG_PATH/logs/current directory before zeekctl can get to it. zeekctl wants the current directory to be a symlink to whatever the current logs directory is, but zeek_carve_logger.py has already created it. This causes zeekctl to abort on startup because it can't update the current symlink.
The solution is to not try to hijack that directory for use by my fakey signatures log file. Instead, I'll put it in a static directory under $ZEEK_LOG_PATH and point filebeat to look there as well.
The text was updated successfully, but these errors were encountered:
mmguero
added
bug
Something isn't working
carving
Relating to carving (extraction) of files from traffic and the scanning of those files
zeek
Relating to Malcolm's use of Zeek
sensor
For issues dealing with the Hedgehog OS capture sensor
labels
Feb 4, 2022
v5.2.4 development
- New features
- idaholab#74 (automatically generate Zeek intelligence indicators from STIX/TAXII)
- Improvements
- group MAC addresses and OUI (vendors) into `related.mac` and `related.oui` for easier searching across all fields
- improvements to default anomaly detectors
- Bug fixes
- Fixidaholab#75 (OpenSearch Dashboards loads slowly without network connectivity)
- Fixidaholab#76 (directory creation race condition starting up zeek on sensor which may cause zeekctl to fail)
bugSomething isn't workingcarvingRelating to carving (extraction) of files from traffic and the scanning of those filessensorFor issues dealing with the Hedgehog OS capture sensorzeekRelating to Malcolm's use of Zeek
This morning I discovered an issue where the
zeek_carve_logger.py
script (which logs hits for files scanned by zeek intosignatures(_carved).log
). This script would end up creating the$ZEEK_LOG_PATH/logs/current
directory beforezeekctl
can get to it.zeekctl
wants thecurrent
directory to be a symlink to whatever the current logs directory is, butzeek_carve_logger.py
has already created it. This causeszeekctl
to abort on startup because it can't update thecurrent
symlink.The solution is to not try to hijack that directory for use by my fakey signatures log file. Instead, I'll put it in a
static
directory under$ZEEK_LOG_PATH
and point filebeat to look there as well.The text was updated successfully, but these errors were encountered: