mirror of
https://github.com/nmap/nmap.git
synced 2026-01-11 00:49:02 +00:00
Minor wording changes to improve the flow of the opening few
paragraphs. I'll be going through the rest of the chapter if time permits.
This commit is contained in:
@@ -13,7 +13,7 @@
|
||||
growing and diverse set of scripts distributed with Nmap, or write
|
||||
their own to meet custom needs.</para>
|
||||
|
||||
<para>Tasks we had in mind when creating the system include:</para>
|
||||
<para>NSE was designed to be versatile so these are some of the tasks we had in mind when creating the system:</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
@@ -36,11 +36,11 @@
|
||||
is able to recognize thousands of different services through
|
||||
its probe and regular expression based matching system, but it
|
||||
cannot recognize everything. For example, identifying the Skype v2 service requires two
|
||||
independent probes. Nmap could also recognize more SNMP services
|
||||
independent probes which version detection isn't flexible enough to handle. Nmap could also recognize more SNMP services
|
||||
if it tried a few hundred different community names by brute
|
||||
force. Neither of these tasks are well suited to traditional
|
||||
Nmap version detection, but both are easily accomplished with
|
||||
NSE. For these reasons, version detection now calls NSE by
|
||||
Nmap version detection but are particularly easy accomplish with
|
||||
NSE. Because of this, version detection now seamlessly calls NSE by
|
||||
default to handle some tricky services. This is described in
|
||||
<xref linkend="nse-vscan"/>.</para>
|
||||
|
||||
@@ -55,7 +55,12 @@
|
||||
<para>When a new vulnerability is discovered, you often want
|
||||
to scan your networks quickly to identify vulnerable systems
|
||||
before the bad guys do. While Nmap isn't a
|
||||
comprehensive <ulink role="hidepdf" url="http://sectools.org/vuln-scanners.html">vulnerability scanner</ulink>, we plan to distribute scripts for some very severe or common vulnerabilities and misconfigurations.</para>
|
||||
comprehensive <ulink role="hidepdf" url="http://sectools.org/vuln-scanners.html">vulnerability scanner</ulink>,
|
||||
NSE is powerful enough to handle even demanding vulnerability
|
||||
checks. A few vulnerability detection scripts have already been
|
||||
written and we plan to distribute additional scripts for very severe
|
||||
or common vulnerabilities and misconfigurations.
|
||||
</para>
|
||||
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -72,7 +77,7 @@
|
||||
posted an Nmap version detection probe and
|
||||
signature so that others could quickly scan their networks.
|
||||
For more complex worms and backdoors, NSE is needed
|
||||
instead.
|
||||
for reliable detection.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@@ -80,7 +85,7 @@
|
||||
<term>Vulnerability exploitation</term>
|
||||
<listitem>
|
||||
<para>
|
||||
As a general scripting language, NSE could even
|
||||
As a general scripting language, NSE can even
|
||||
be used to exploit vulnerabilities rather than just find them.
|
||||
The capability to add custom exploit scripts may be valuable
|
||||
for some people (particularly
|
||||
|
||||
Reference in New Issue
Block a user