mirror of
https://github.com/nmap/nmap.git
synced 2026-08-03 22:29:06 +00:00
note that --packet-trace enables --script-trace too
This commit is contained in:
parent
d082ff870f
commit
75e11edf2c
1 changed files with 5 additions and 2 deletions
|
|
@ -2106,7 +2106,8 @@ subtable is usually named after the script (like
|
|||
displayed information includes the communication protocol, the
|
||||
source, the target and the transmitted data. If more than 5% of all
|
||||
transmitted data is not printable, then the trace output is in a hex
|
||||
dump format.
|
||||
dump format. Specifying <option>--packet-trace</option> enables script
|
||||
tracing too.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
@ -3411,7 +3412,9 @@ even if this option is not specified.
|
|||
thousands of lines, you may want to specify a limited
|
||||
number of ports to scan, such as <option>-p20-30</option>. If you only care
|
||||
about the goings on of the version detection subsystem, use
|
||||
<option>--version-trace</option> instead.</para>
|
||||
<option>--version-trace</option> instead. If you only care about script tracing,
|
||||
specify <option>--script-trace</option>. With <option>--packet-trace</option>, you get
|
||||
all of the above.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue