scanning

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

Hey, here we need add url decoding cuz that invalid link with symbols of get request like ?, &, = etc

p.s thx for awesome tool

RITA does not store information on how long an import took or how much data was processed in an import.

This ticket is to implement, at a minimum, those metrics mentioned above into the RITA logging.

This bar with log4j doesn't show when a search request is pending.

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