Package: nmap
Version: 4.00-2
Severity: minor
The documentation mentions --max_scan-delay and --max-scan-delay while
only --max-scan-delay is valid. See the attached patch-file.
*** nmap-4.00_docs-typo.patch
diff -uNr a/nmap-4.00/docs/nmap.1 b/nmap-4.00/docs/nmap.1
--- a/nmap-4.00/docs/nmap.1 2006-01-30 08:15:44.000000000 +0100
+++ b/nmap-4.00/docs/nmap.1 2006-04-13 10:59:43.575062609 +0200
@@ -819,7 +819,7 @@
30m
to ensure that Nmap doesn't waste more than half an hour on a single host.
Note that Nmap may be scanning other hosts at the same time during that half an
hour as well, so it isn't a complete loss. A host that times out is skipped. No
port table, OS detection, or version detection results are printed for that
host.
.TP
-\fB\-\-scan\-delay <time>\fR; \fB\-\-max_scan\-delay <time>\fR (Adjust delay
between probes)
+\fB\-\-scan\-delay <time>\fR; \fB\-\-max-scan\-delay <time>\fR (Adjust delay
between probes)
This option causes Nmap to wait at least the given number of milliseconds
between each probe it sends to a given host. As with many other timing options,
you can append
s,
m, or
@@ -831,7 +831,7 @@
will keep Nmap at that slow rate. Nmap tries to detect rate limiting and
adjust the scan delay accordingly, but it doesn't hurt to specify it explicitly
if you already know what rate works best.
.sp
When Nmap adjusts the scan delay upward to cope with rate limiting, the scan
slows down dramatically. The
-\fB\-\-max_scan\-delay\fR
+\fB\-\-max-scan\-delay\fR
option specifies the largest delay that Nmap will allow. Setting this value
too low can lead to wasteful packet retransmissions and possible missed ports
when the target implements strict rate limiting.
.sp
Another use of
diff -uNr a/nmap-4.00/docs/nmap-man.xml b/nmap-4.00/docs/nmap-man.xml
--- a/nmap-4.00/docs/nmap-man.xml 2006-01-28 09:08:56.000000000 +0100
+++ b/nmap-4.00/docs/nmap-man.xml 2006-04-13 10:59:57.032220330 +0200
@@ -1901,7 +1901,7 @@
<varlistentry>
<term>
<option>--scan-delay <time></option>;
- <option>--max_scan-delay
+ <option>--max-scan-delay
<time></option> (Adjust delay between probes)</term>
<listitem>
@@ -1921,7 +1921,7 @@
<para>When Nmap adjusts the scan delay upward to cope with rate
limiting, the scan slows down dramatically. The
-<option>--max_scan-delay</option> option specifies the largest delay
+<option>--max-scan-delay</option> option specifies the largest delay
that Nmap will allow. Setting this value too low can lead to wasteful
packet retransmissions and possible missed ports when the target
implements strict rate limiting.</para>
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (300, 'unstable'), (200, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.6
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages nmap depends on:
ii libc6 2.3.5-13 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-9 GCC support library
ii libpcre3 6.4-1.1 Perl 5 Compatible Regular Expressi
ii libssl0.9.8 0.9.8a-7 SSL shared libraries
ii libstdc++6 4.0.2-9 The GNU Standard C++ Library v3
nmap recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
