Tim Wojtulewicz
Tim Wojtulewicz
Another issue that cropped up while I was fixing this. I get this error message: ``` error in and ./tags.zeek, line 30: 1 type clash (enum and Files::ANALYZER_X509) ``` That...
@initconf Have you seen this one pop up again at all? Do you happen to know what it was reading at the time? The `count` value from this line looks...
> This might be the inverse of getting access to all packets that we not processed, per https://github.com/zeek/zeek/discussions/1595 . This is certainly easy, but not by UID. That'd be quite...
As a data point, I spun up an arm64 AWS instance and was able to build without any issues. uname: ``` Linux ip-snip 5.15.0-1009-aws #11-Ubuntu SMP Thu May 26 19:39:49...
At least we're now getting a warning for the test case in the first post, thanks to Vern's recent work: > warning in ./test.zeek, line 3: handler for non-existing event...
I don't believe we keep any information about what interface a packet came in from currently in the code. It would depend on whatever packet source plugin you're using having...
I have some questions about how we'd handle this in relation to endianness. For example, take these two tests from `bifs/bytestring_to_count.zeek`: ``` print bytestring_to_count("\x00\x00\xff\xff", F); # 65535 print bytestring_to_count("\xff\xff\x00\x00", T);...
@vbr-cts How's this going? is there an external package you can link to here just for the historical information? Can I close out this issue?
So just so I'm clear, this is an issue with `print` not outputting utf-8 correctly? `to_json` is fine and does the right thing?
I changed the title of this GHI to match the actual issue.