PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2025-12-26 17:39:03 +00:00
Code Issues Projects Releases Wiki Activity

document new script force feature

Browse Source
This commit is contained in:
fyodor
2011-12-19 21:07:01 +00:00
parent 21921dae6b
commit 59f8b931f1
2 changed files with 34 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/refguide.xml
View File

@@ -2241,7 +2241,7 @@ way.</para>
<varlistentry>
<term>
<option>--script <replaceable>filename</replaceable>|<replaceable>category</replaceable>|<replaceable>directory</replaceable>|<replaceable>expression</replaceable>|all<optional>,...</optional></option>
<option>--script <replaceable>filename</replaceable>|<replaceable>category</replaceable>|<replaceable>directory</replaceable>|<replaceable>expression</replaceable><optional>,...</optional></option>
<indexterm><primary><option>--script</option></primary></indexterm>
</term>
@@ -2252,9 +2252,16 @@ Runs a script scan using the comma-separated list of filenames, script
categories, and directories. Each element in the list may also be a
Boolean expression describing a more complex set of scripts. Each
element is interpreted first as an expression, then as a category, and
finally as a file or directory name. The special argument
<literal>all</literal> makes every script in Nmap's script database
eligible to run. The <literal>all</literal> argument should be used with caution as NSE may contain dangerous scripts including exploits, brute force authentication crackers, and denial of service attacks.
finally as a file or directory name.</para>
<para>There are two special features for advanced users only.
One is to prefix script names and expressions with
<literal>+</literal> to force them to run even if they normally
wouldn't (e.g. the relevant service wasn't detected on the target
port). The other is that the argument <literal>all</literal> may be
used to specify every script in Nmap's database. Be cautious with
this because NSE contains dangerous scripts such as exploits, brute
force authentication crackers, and denial of service attacks.
</para>
<para>

26
docs/scripting.xml
View File

@@ -619,7 +619,7 @@ Black Hat Briefings in 2010.</para>
<varlistentry>
<term>
<indexterm><primary><option>--script</option></primary></indexterm>
<option>--script <replaceable>filename</replaceable>|<replaceable>category</replaceable>|<replaceable>directory</replaceable>|<replaceable>expression</replaceable>|all<optional>,...</optional></option></term>
<option>--script <replaceable>filename</replaceable>|<replaceable>category</replaceable>|<replaceable>directory</replaceable>|<replaceable>expression</replaceable><optional>,...</optional></option></term>
<listitem>
@@ -633,10 +633,24 @@ finally as a file or directory name. The special argument
eligible to run. The <literal>all</literal> argument should be used with caution as NSE may contain dangerous scripts including exploits, brute force authentication crackers, and denial of service attacks.
</para>
<para>
Each element in the script expression list may be prefixed with a
<literal>+</literal> character to force the given script(s) to run
regardless of the conditions in their <literal>prerule</literal> or
<literal>hostrule</literal> functions. This is generally only done by
advanced users in special cases. For example, you might want to do a
configuration review on a bunch of MS SQL servers, some of which are
running on nonstandard ports. Rather than slow the Nmap scan by
running extensive version detection (<option>-sV
--version-all</option>) so that Nmap will recognize the ms-sql
service, you can force the ms-sql-config script to run against all the
targetted hosts and ports by specifying <option>--script
+ms-sql-config</option>.</para>
<para>
File and directory names may be relative or absolute. Absolute names are
used directly. Relative paths are looked for in the
<filename>scripts</filename> of each of the following places until
used directly. Relative paths are searched for in the
<filename>scripts</filename> subdirectory of each of the following places until
found:
<indexterm><primary>data files</primary><secondary>directory search order</secondary></indexterm><indexterm><primary>scripts, location of</primary></indexterm>
<simplelist>
@@ -1214,6 +1228,12 @@ NSE: Script Scanning completed.
to run against a port. Example rules are shown in <xref
linkend="nse-tutorial-rule"/>.
</para>
<para>Advanced users may force a script to run regardless of the
results of these rule functions by prefixing the script name (or
category or other expression) with a <literal>+</literal> in the
<option>--script</option> argument.</para>
<para>
The current standard to choose between a
<literal>prerule</literal> or a <literal>postrule</literal> is