Having nothing better to do I copied and pasted text from the man pages at
http://insecure.org/nmap/man/ into OOo and here is what I found:
In http://insecure.org/nmap/man/man-os-detection.html
Tells Nmap to only use the old OS detection system. If -O2 just gives you
a fingerprint to submit, but you don't know what OS the target is running, try
-O1. But in that case, don't submit the fingeprint as you don't know for sure
whether -O1 guess correctly. If it was perfect, we wouldn't have bothered to
create -O2.
This option, and all other vestigates of the old OS detection system, will
likely be removed in late 2006 or in 2007.
FIX: Change 'fingeprint' to 'fingerprint' and 'vestigates' to 'vestiges'
In http://insecure.org/nmap/man/man-performance.html
Some hosts simply take a long time to scan. This may be due to poorly
performing or unreliable networking hardware or software, packet rate limiting,
or a restrictive firewall. The slowest few percent of the scanned hosts can eat
up a majority of the scan time. Sometimes it is best to cut your losses and
skip those hosts initially. Specify --host-timeout with the maximum amoung of
time you are willing to wait.
FIX: Change 'amoung' to 'amount'
In http://insecure.org/nmap/man/man-bypass-firewalls-ids.html
The IP protocol offers several options which may be placed in packet
headers. Unlike the ubiquitous TCP options, IP options are rarely seen due to
practicality and security concerns. In fact, many Internet routers block the
most dangerous options such as source routing. Yet options can still be useful
in some cases for determining and manipulating the network route to target
machines. For example, you may be able to use the record route option to
determine a patch to a target even when more tranditional traceroute-style
approaches fail.
FIX: Change 'patch' to 'path' and 'tranditional' to 'traditional'
In http://insecure.org/nmap/man/man-bugs.html
Read this full munaual page as well. If nothing comes of this, mail a bug
report to <nmap-dev_at_insecure.org>.
FIX: Change 'munaual' to 'manual'
I also stripped the xml tags from the man page source file nmap-man.xml and
searched through it, and found 'fingeprint', 'vestigates', 'amoung', 'patch',
'tranditional', and 'munaual'. It has the same errors as the web version. I
have included a patch. It is my first time submitting a patch for anything, so
I hope I have done it right, it is a diff against nmap-man.xml in the docs
directory (taken from 4.20ALPHA8). The only changes I made were the six word
corrections. I assume that the man page itself (nmap.1) will need to be
regenerated, but I don't feel comfortable doing that so I will leave that to a
developer.
Peter Oven
--- nmap-man.xml 2006-10-12 11:56:24.000000000 -0700
+++ nmap-man.xml.original 2006-10-12 11:33:13.000000000 -0700
@@ -1787,12 +1787,12 @@
<para>Tells Nmap to only use the old OS detection system.
If <option>-O2</option> just gives you a fingerprint to
submit, but you don't know what OS the target is running,
- try <option>-O1</option>. But in that case, <emphasis role="bold">don't submit the fingerprint</emphasis> as you
+ try <option>-O1</option>. But in that case, <emphasis role="bold">don't submit the fingeprint</emphasis> as you
don't know for sure whether <option>-O1</option> guess
correctly. If it was perfect, we wouldn't have bothered to
create <option>-O2</option>.</para>
- <para>This option, and all other vestiges of the old OS
+ <para>This option, and all other vestigates of the old OS
detection system, will likely be removed in late 2006 or in
2007.</para>
@@ -2044,7 +2044,7 @@
slowest few percent of the scanned hosts can eat up a majority of the
scan time. Sometimes it is best to cut your losses and skip those
hosts initially. Specify
-<option>--host-timeout</option> with the maximum amount of time you
+<option>--host-timeout</option> with the maximum amoung of time you
are willing to wait. I
often specify <literal moreinfo="none">30m</literal> to ensure that Nmap doesn't waste
more than half an hour on a single host. Note that Nmap may be
@@ -2468,8 +2468,8 @@
such as source routing. Yet options can still be useful in some
cases for determining and manipulating the network route to
target machines. For example, you may be able to use the record
- route option to determine a path to a target even when more
- traditional traceroute-style approaches fail. Or if your
+ route option to determine a patch to a target even when more
+ tranditional traceroute-style approaches fail. Or if your
packets are being dropped by a certain firewall, you may be able
to specify a different route with the strict or loose source
routing options.</para>
@@ -3347,7 +3347,7 @@
version available from <ulink url="http://insecure.org/nmap/"/>. If the problem persists,
do some research to determine whether it has already been
discovered and addressed. Try Googling the error message or
- browsing the Nmap-dev archives at <ulink url="http://seclists.org/"/>. Read this full manual page as
+ browsing the Nmap-dev archives at <ulink url="http://seclists.org/"/>. Read this full munaual page as
well. If nothing comes of this, mail a bug report to
<email>nmap-dev_at_insecure.org</email>. Please include everything
you have learned about the problem, as well as what version of
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org
Received on Oct 12 2006
Intro
