nmap

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

Right now, whenever Zenmap crashes, it gives the user a stack trace and asks the user to send it to the Nmap dev list. So we get a flood of emails (most of which aren't even allowed through moderation) which often contain just a stack trace with no subject line or any explanatory text in the message body. Lots of these are for well known issues in older versions of Zenmap. So it's not very usef

im getting this error

how can i fix this

See LeakIX/l9format.

Even though it has a convenient converter (LeakIX/l9filter), supporting its output might be useful.

my docker api version is 1.37 ,Echo is Docker API was unreachable: Error response from daemon: client version 1.39 is too new. Maximum supported API version is 1.37 ;Docker API was unreachable:error during connect: Get "http://00:0C:29:C6:5D:36:2375/v1.39/info": dial tcp: lookup 00:0C:29:C6:5D:36: no such host

Hi,

Appreciate sharing this stylesheet with us.

I am encountering a visual error. As you can see 2 ports are open, however they are not reported in the summary table.

Also for some reason the IP is reported multiple times

Nice project! One nice-to-have would be support of the -oX parameter. I see the option to output in greppable format (-oG) but not XML.