mirror of
https://github.com/nmap/nmap.git
synced 2026-01-24 23:29:04 +00:00
More proofreading from indexing of the final chapters.
This commit is contained in:
@@ -413,10 +413,11 @@ searched in the following places until found:
|
||||
<indexterm><primary>scripts</primary><secondary>location of</secondary></indexterm>
|
||||
<filename>--datadir/</filename>;
|
||||
<indexterm><primary><envar>NMAPDIR</envar> environment variable</primary></indexterm>
|
||||
<filename>$(NMAPDIR)/</filename>;
|
||||
<filename>~user/nmap/</filename> (not searched on Windows);
|
||||
<indexterm><primary><filename>NMAPDATADIR</filename></primary></indexterm>
|
||||
<filename>NMAPDATADIR/</filename> or
|
||||
<filename>$NMAPDIR/</filename>;
|
||||
<indexterm><primary sortas="nmap"><filename>.nmap</filename> directory</primary></indexterm>
|
||||
<filename>~/.nmap/</filename> (not searched on Windows);
|
||||
<indexterm><primary>NMAPDATADIR</primary></indexterm>
|
||||
NMAPDATADIR/ or
|
||||
<filename>./</filename>. A <filename>scripts/</filename> subdirectory
|
||||
is also tried in each of these. Give the argument <literal>all</literal> to execute all scripts in the Nmap script database.
|
||||
</para>
|
||||
@@ -732,7 +733,7 @@ that.</para>
|
||||
use, small in size, compatible with the Nmap license,
|
||||
scalable, fast and parallelizable. There have been several
|
||||
efforts to design a security auditing language from scratch
|
||||
which have resulted in well known awkward solutions. It was
|
||||
which have resulted in well-known awkward solutions. It was
|
||||
clear from the beginning that we would not go down this
|
||||
road. For a while the Guile scheme interpreter was considered
|
||||
but the preference drifted towards Elk in favor of its more
|
||||
@@ -740,7 +741,7 @@ that.</para>
|
||||
difficult. In addition, the subset of Nmap users familiar with
|
||||
functional programming is regarded too small to consider
|
||||
Scheme as an option. Larger interpreters like Perl, Python or
|
||||
Ruby are well known and loved, but are difficult to embed
|
||||
Ruby are well-known and loved, but are difficult to embed
|
||||
efficiently. In the end, Lua exceeded in all criteria for
|
||||
NSE. It is small, distributed under the MIT license, has
|
||||
coroutines for efficient parallel script
|
||||
@@ -1179,7 +1180,7 @@ if(s) code_to_be_done_on_match end
|
||||
<para>
|
||||
checks whether an IP address, provided as a string in
|
||||
dotted-quad notation, is part of the non-routed private IP address
|
||||
space, as described in <ulink role="hidepdf" url="http://www.rfc-editor.org/rfc/rfc1918.txt">RFC 1918</ulink>. These addresses are the well known
|
||||
space, as described in <ulink role="hidepdf" url="http://www.rfc-editor.org/rfc/rfc1918.txt">RFC 1918</ulink>. These addresses are the well-known
|
||||
<literal>10.0.0.0/8</literal>, <literal>192.168.0.0/16</literal> and
|
||||
<literal>172.16.0.0/12</literal> networks.
|
||||
</para>
|
||||
@@ -1251,7 +1252,7 @@ if(s) code_to_be_done_on_match end
|
||||
<listitem>
|
||||
<para>
|
||||
This is a combination of the above functions, since many scripts
|
||||
explicitly try to run against the well known ports, but want
|
||||
explicitly try to run against the well-known ports, but want
|
||||
also to run against any other port which was discovered to run the
|
||||
named service. A typical example for this function is:
|
||||
<literal>portrule = shortport.port_or_service(22,"ssh")</literal>.
|
||||
@@ -3536,7 +3537,7 @@ require "shortport"
|
||||
</programlisting>
|
||||
|
||||
<para>We want to check whether the service behind the port is finger,
|
||||
or whether it runs on finger's well known port 79. Through this we can
|
||||
or whether it runs on finger's well-known port 79. Through this we can
|
||||
use the information gathered during the version scan (if finger runs
|
||||
on a non-standard port) or still run against at least the port we
|
||||
expect it, should the version detection information not be available.</para>
|
||||
|
||||
Reference in New Issue
Block a user