PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2025-12-16 20:59:02 +00:00
Code Issues Projects Releases Wiki Activity

Rewrite the --script-timeout documentation text (even though this option, which was added last year, isn't currently working for me) and also made another slight typo fix to --max-retries doc. This was all suggested by @meetinthemiddle-be on Github. Closes #992.

Browse Source
This commit is contained in:
fyodor
2017-09-07 22:18:08 +00:00
parent afcd81bc7d
commit 0f19c7228f
1 changed files with 12 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/refguide.xml
View File

@@ -2746,7 +2746,7 @@ lost on the network. It is also possible that the target host has
rate limiting enabled that temporarily blocked the response. So Nmap rate limiting enabled that temporarily blocked the response. So Nmap
tries again by retransmitting the initial probe. If Nmap detects poor tries again by retransmitting the initial probe. If Nmap detects poor
network reliability, it may try many more times before giving up on a network reliability, it may try many more times before giving up on a
port. While this benefits accuracy, it also lengthen scan times. port. While this benefits accuracy, it also lengthens scan times.
When performance is critical, scans may be sped up by limiting the When performance is critical, scans may be sped up by limiting the
number of retransmissions allowed. You can even specify number of retransmissions allowed. You can even specify
<option>--max-retries 0</option> to prevent any retransmissions, <option>--max-retries 0</option> to prevent any retransmissions,
@@ -2801,13 +2801,17 @@ for that host.</para>
</term> </term>
<listitem> <listitem>
<para>Some scripts take <emphasis>long</emphasis> time before they complete their execution, this can happen due to many reasons <para>While some scripts complete in fractions of a second,
maybe some bug in script, delay in the network or nature of the script itself(example:http-slowloris). others can take hours or more depending on the nature of the
If you want to keep some limit on time for which script should run then you need to specify script, arguments passed in, network and application
<option>--script-timeout</option> with the maximum amount of time conditions, and more. The <option>--script-timeout</option>
for which script should be run. Note that all scripts will have same timeout. Once script gets timed out option sets a ceiling on script execution time. Any script
no output for that script will be shown. Whether a script has timed out or not, can be seen in debug output. instance which exceeds that time will be terminated and no
</para> output will be shown. If debugging (<option>-d</option>) is
enabled, Nmap will report on each timeout. For host and
service scripts, a script instance only scans a single
target host or port and the timeout period will be reset for
the next instance.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>