CLI option to also show closed ports

[fabianbees]

This PR introduces the new CLI option --closed, which enables the option to also show ports which are closed.

From a security perspective, it is very useful information to see whether we got any response at all for a given port, even when the response is a RST (conn-refused).
It can indicate that our request was denied (or specifically blocked by a firewall).

Currently this behavior is behind the --closed CLI flag and not enabled by default.
Nmap, for example, shows closed ports by default.

Regarding the output of the --closed option, it mimics the output for open ports, but instead of Open it shows Closed right before the IP Address.

If the -g (grepable) option is set, first all open ports are printed for each IPs, then the text closed ports: is printed and the same output is repeated for all closed ports.

Here is an example:

.----. .-. .-. .----..---.  .----. .---.   .--.  .-. .-.
| {}  }| { } |{ {__ {_   _}{ {__  /  ___} / {} \ |  `| |
| .-. \| {_} |.-._} } | |  .-._} }\     }/  /\  \| |\  |
`-' `-'`-----'`----'  `-'  `----'  `---' `-'  `-'`-' `-'
The Modern Day Port Scanner.
________________________________________
: http://discord.skerritt.blog         :
: https://github.com/RustScan/RustScan :
 --------------------------------------
TreadStone was here 🚀

[~] The config file is expected to be at "/********/.rustscan.toml"
[~] Automatically increasing ulimit value to 50000.
Closed [10.100.0.1]:22
Open [10.100.0.1]:2222
10.100.0.1 -> [2222]
closed ports:
10.100.0.1 -> [22]

And with the -g option:

10.100.0.1 -> [2222]
closed ports:
10.100.0.1 -> [22]

[fabianbees]

I have rebased the feature onto master.

[fabianbees]

@bee-san Can you please also have a look at this PR?

[bee-san]

thanks for this! has a merge conflict :(

[fabianbees]

Hi @bee-san, I have rebased this PR again onto master, so no more merge conflicts anymore.

Can you please have another look? I am looking forward in getting this merged, thank you!

[bee-san]

Thanks @fabianbees, and sorry it took so long! Seeing RSTs really is useful for spotting firewalls. The scanner and main had changed a lot on master, so I re-applied your feature on top, credited to you, with a few changes to keep it safe and non-breaking:

• No change without --closed. Before, refused connections were returned as Closed on every scan. That cost memory on full-range scans (up to 65k closed entries) and hid the 'no open ports found' hint for hosts that only reject. Now they're only collected when --closed is set.
• Scripts only run on open ports. print_summary would have started the default nmap script against closed ports. Closed ports are now only printed: live as Closed ip:port, then in your closed ports: summary.
• No library API break. Scanner::new() and run() keep their signatures. Scanner::with_closed_ports() and run_with_status() -> Vec<PortStatus> are new, following the builder pattern from #916.

CI is green on all four platforms.

[fabianbees]

Excellent, thank you very much for having a look at this.