Updated Frequently Asked Questions (markdown)

Tib3rius 2022-06-10 12:59:23 -04:00
parent b55e30389e
commit 069e2e9292
1 changed files with 1 additions and 1 deletions

@ -8,7 +8,7 @@ It is entirely possible that one command (usually a full TCP Nmap scan or direct
The port scans are performed using Nmap, which tries to be "safe" when scanning by not flooding the network with large amounts of packets. There is always a trade off between speed and accuracy when it comes to port scanning. However, this does mean that by default, Nmap can be slow. AutoRecon does run Nmap with `-T4` which is the second highest "timing template" available, which should increase the speed, however it doesn't go beyond that.
Luckily, one of the core principles of AutoRecon v2 is that users should be able to easily configure commands to their liking. As a result, there is an `--nmap-append` command line option, which allows the user to pass extra arguments to every Nmap command. For example, you could run AutoRecon with `--nmap-append="-T5"` to use the fastest timing template, or even set `--nmap-append="--min-rate=5000"` which tells Nmap to send at least 5000 packets per second.
Luckily, one of the core principles of AutoRecon v2 is that users should be able to easily configure commands to their liking. As a result, there is an `--nmap-append` command line option, which allows the user to pass extra arguments to every Nmap command. For example, you could run AutoRecon with `--nmap-append="-T5"` to use the fastest timing template, or even set `--nmap-append="--min-rate=5000 --min-parallelism=5000"` which tells Nmap to send at least 5000 packets per second, and scan 5000 ports concurrently.
# Why did AutoRecon miss <insert port/service here>?