nmap

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

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

Hiya,

As previously discussed with @0xtavian , this request is being made because of errors I have encountered when using it in an active environment. I have a machine which doesn't have a public ip's, therefore when trying to execute any command, the sshconfig that is generated is malformed because of a missing HostName field value.

So the suggestion is basically to make it so the sshconfig

The current view is "15 Most Common Product/Ports"
Only seeing 15 Products limits the visibility into network recon.

Request is to add the option to "Show All Products Ports"
The ability to see all products is key to network enumeration.

![image](https

ndiff --xml nmap_scan1.xml nmap_scan2.xml

https://nmap.org/book/ndiff-man-output.html

ndiff can generate diffs between two scans, can you write a template to beautify the ndiff output?