Closed canarieids closed 1 year ago
I was able to reproduce this locally, I'll see if I can figure out what changed in 5.x that is causing this.
It's related to the changes in Zeek 5 to move from using the tx_hosts
, rx_hosts
, and conn_uids
fields in files.log
and to standardize on the uid
and id.[orig|resp]
fields, instead.
As a short-term workaround, you can try also inserting the following in your local.zeek
to return those fields and remove the errors:
@load policy/frameworks/files/deprecated-txhosts-rxhosts-connuids.zeek
Thank you we are testing this on our side shortly.
Thank you this solution worked!
FYI, I have updated the script to be able to run in Zeek 4, 5, and 6. The hack described above for Zeek 5 should not be necessary with this new version. Also, that hack does not work for Zeek 6, so for Zeek 6 or newer, the new script will be necessary.
We installed on Zeek version 5.1.1 using Zeek Package Manager (zkg install zeek/corelight/detect-ransomware-filenames).
When we try to load the package we get the following error:
"
"