Thomas Strömberg

It's currently managed by the firewall, which doesn't make much sense.

Need to setup figure out if I can delegate to name.com, or we need to run my own NS for this.

The generic terminology of "level" and "score" was not self-describing. This changes our flags to specifically mention "risk". TODO(tstromberg): Add alias to avoid unnecessary breakage. Fixes #231

Rename *-level flags with *-risk

1

It isn't obvious what the level flag references. --min-level should be --min-risk, for example

It should answer: - [ ] How to build bincapz - [ ] How to run tests - [ ] How to modify an existing rule - [ ] How...

We're using Wolfi as a benchmark open-source repo. There are a dozen or so CRITICAL false positives that exist, mainly relating to Python code.

Reference: https://www.bitdefender.com/blog/hotforsecurity/kaiji-new-strain-iot-malware-seizing-control-launching-ddos-attacks/

https://blog.xlab.qianxin.com/8220-k4spreader-new-tool-en/ There are some particular shell invocations that seem of interest.

Rename project?

6

When this project first began, it focused on enumerating binaries' capabilities. It's since grown in two ways: - We've shifted capability detection to focus on those that may be used...