On Oct 31, 2019, at 3:33 PM, Justin Azoff
On Thu, Oct 31, 2019 at 5:55 PM James Lay
Well here I am. Zeek 3 was released Sep 23rd,
and I'm dead in the water
until these are updated:
appears to work just fine.
Other than a warning about using bro_init, works fine. The code that causes this looks
like dead code that isn't even used anyway, so they can just be deleted.
There's also the hosom/bro-ja3 which is a cleaned up version and works without
warnings. The test suite it includes fails to run properly (fixable btest issues), but
installing anyway results in a functional package.
Looks like this hits the issue where it depends on bro/something which are now all
zeek/something I fixed this in one of my packages by just deleting the "bro/"
part of the dependency but I think this is more a migration issue that zkg could help
if anyone has inside communication channels or
some other form of
digital cattle prod I'd love it if you could motivate the above to get
to Zeek 3 compatibility. Truth be told I haven't even been able to
start testing yet due to the missing plugins I use.
Well, 2 out of the 3 already work, and one just needs a minor update that I'm sure
Jan would be happy to make if someone had just told him about it.
Zeek mailing list