A great resource of various types of sensitive keys can be found here: https://gist.github.com/EdOverflow/8bd2faad513626c413b8fc6e9d955669

RustScan has an accessible mode, rustscan --accessible which should promise not to have any weird ASCII text in it.

Write CI that runs RustScan with --accessible a few times, with different flags / options and check the terminal output to see if it contains one of these:

1. [!]
2. [~]
3. [>]
4. | {}

If any of these characters appear in any of the tests, fail the CI. E

So instead of having to do rita import --config etc/rita.yaml ... we would do rita --config etc/rita.yaml import .... This makes it easier to modify most commands since --config is less likely to change than the rita subcommand. It also makes it possible to create aliases like:

• alias rita1=rita --config /etc/rita/config1.yaml
• alias rita2=rita --config /etc/rita/config2.yaml

Wher

Hi,

It would be interesting to have those new rules integrated in ChopChop, see : https://github.com/nnposter/nndefaccts/blob/master/http-default-accounts-fingerprints-nndefaccts.lua