1
0
mirror of https://github.com/nmap/nmap.git synced 2025-12-17 21:19:01 +00:00

changes to os detection chapter

This commit is contained in:
fyodor
2006-08-08 07:44:16 +00:00
parent d32123bd54
commit 2d36c91639
5 changed files with 18 additions and 11 deletions

View File

@@ -2,7 +2,7 @@
.\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
.\" Instead of manually editing it, you probably should edit the DocBook XML
.\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
.TH "NMAP" "1" "08/01/2006" "" "Nmap Reference Guide"
.TH "NMAP" "1" "08/07/2006" "" "Nmap Reference Guide"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
@@ -260,8 +260,8 @@ to skip host discovery and port scan all target hosts. The following options con
.TP
\fB\-sL\fR (List Scan)
The list scan is a degenerate form of host discovery that simply lists each host of the network(s) specified, without sending any packets to the target hosts. By default, Nmap still does reverse\-DNS resolution on the hosts to learn their names. It is often surprising how much useful information simple hostnames give out. For example,
fw.chi.playboy.com
is the firewall for the Chicago office of Playboy Enterprises. Nmap also reports the total number of IP addresses at the end. The list scan is a good sanity check to ensure that you have proper IP addresses for your targets. If the hosts sport domain names you do not recognize, it is worth investigating further to prevent scanning the wrong company's network.
fw.chi
is the name of one company's Chicago firewall. Nmap also reports the total number of IP addresses at the end. The list scan is a good sanity check to ensure that you have proper IP addresses for your targets. If the hosts sport domain names you do not recognize, it is worth investigating further to prevent scanning the wrong company's network.
.sp
Since the idea is to simply print a list of target hosts, options for higher level functionality such as port scanning, OS detection, or ping scanning cannot be combined with this. If you wish to disable ping scanning while still performing such higher level functionality, read up on the
\fB\-P0\fR
@@ -368,20 +368,24 @@ or
\fB\-n\fR (No DNS resolution)
Tells Nmap to
\fInever\fR
do reverse DNS resolution on the active IP addresses it finds. Since DNS is often slow, this speeds things up.
do reverse DNS resolution on the active IP addresses it finds. Since DNS can be slow even with Nmap's built\-in parallel stub resolver, this option can slash scanning times.
.TP
\fB\-R\fR (DNS resolution for all targets)
Tells Nmap to
\fIalways\fR
do reverse DNS resolution on the target IP addresses. Normally this is only performed when a machine is found to be alive.
do reverse DNS resolution on the target IP addresses. Normally reverse DNS is only performed against responsive (online) hosts.
.TP
\fB\-\-system\-dns\fR (Use system DNS resolver)
By default, Nmap resolves IP addresses by sending queries directly to the name servers configured on your host and then listening for responses. Many requests (often dozens) are performed in parallel for performance. Specify this option if you wish to use your system resolver instead (one IP at a time via the getnameinfo() call). This is slower and rarely useful unless there is a bug in the Nmap DNS code \-\- please contact us if that is the case. The system resolver is always used for IPv6 scans.
By default, Nmap resolves IP addresses by sending queries directly to the name servers configured on your host and then listening for responses. Many requests (often dozens) are performed in parallel to improve performance. Specify this option to use your system resolver instead (one IP at a time via the getnameinfo() call). This is slower and rarely useful unless you find a bug in the Nmap parallel resolver (please let us know if you do). The system resolver is always used for IPv6 scans.
.TP
\fB\-\-dns\-servers <server1[,server2],...> \fR (Servers to use for reverse DNS queries)
By default Nmap will try to determine your DNS servers (for rDNS resolution) from your resolv.conf file (UNIX) or the registry (Win32). Alternatively, you may use this option to specify alternate servers. This option is not honored if you are using
\fB\-\-system\-dns\fR
or an IPv6 scan. Using multiple DNS servers is often faster and more stealthy than querying just one. The best performance is often obtained by specifying all of the authoritative servers for the target IP space.
or an IPv6 scan. Using multiple DNS servers is often faster, especially if you choose authoritative servers for your target IP space. This option can also improve stealth, as your requests can be bounced off just about any recursive DNS server on the internet.
.sp
This option also comes in handy when scanning private networks. Sometimes only a few name servers provide proper rDNS information, and you may not even know where they are. You can scan the network for port 53 (perhaps with version detection), then try Nmap list scans (\fB\-sL\fR) specifying each name server one at a time with
\fB\-\-dns\-servers\fR
until you find one which works.
.SH "PORT SCANNING BASICS"
.PP
While Nmap has grown in functionality over the years, it began as an efficient port scanner, and that remains its core function. The simple command

View File

@@ -1247,7 +1247,8 @@ match rpd m|^\+host=cashew version=([\d.]+) uptime=[\d+:]+ audio-bits=\d+ audio-
# Simple Asynchronous File Transfer (SAFT)
match saft m|^220 ([\w-.]+) SAFT server \(sendfiled ([\w.]+) on ([\w]+)\) ready\.\r\n| p/sendfiled/ v/$2/ h/$1/ o/$3/
match scanager m|^\*\*\* ITSO_DB_FAIL \*\*\* invalid request\r\n| p/Indiana University Scanager DB/
match sdmsvc m|^[\xaa\xff]$| p/LANDesk Software Distribution/ i/sdmsvc.exe/ o/Windows/
# This sdmsvc was matching HP printers. May be bogus, so removed.
# match sdmsvc m|^[\xaa\xff]$| p/LANDesk Software Distribution/ i/sdmsvc.exe/ o/Windows/
# http://www.ietf.org/internet-drafts/draft-martin-managesieve-04.txt
match sieve m|^NO Fatal error: Error initializing actions\r\n$| p|Cyrus timsieved| i|included w/cyrus imap|
match sieve m|^\"IMPLEMENTATION\" \"Cyrus timsieved v([\d.]+)-Red Hat [\d.-]+\"\r\n| p|Cyrus timsieved| v/$1/ i|Red Hat; included w/cyrus imap| o/Linux/

View File

@@ -1969,7 +1969,8 @@ hacl-local 5304/udp #
hacl-test 5305/tcp #
hacl-test 5305/udp #
cfengine 5308/tcp #
cfengine 5308/udp #
cfengine 5308/udp #
zeroconf 5353/udp # Mac OS X Bonjour/Zeroconf port
pcduo-old 5400/tcp # RemCon PC-Duo - old port
pcduo 5405/tcp # RemCon PC-Duo - new port
omid 5428/udp # OpenMosix Info Dissemination

View File

@@ -216,6 +216,7 @@ printf("%s %s ( %s )\n"
" --system-dns: Use OS's DNS resolver\n"
"SCAN TECHNIQUES:\n"
" -sS/sT/sA/sW/sM: TCP SYN/Connect()/ACK/Window/Maimon scans\n"
" -sU: UDP Scan\n"
" -sN/sF/sX: TCP Null, FIN, and Xmas scans\n"
" --scanflags <flags>: Customize TCP scan flags\n"
" -sI <zombie host[:probeport]>: Idlescan\n"
@@ -234,8 +235,8 @@ printf("%s %s ( %s )\n"
" --version-trace: Show detailed version scan activity (for debugging)\n"
"OS DETECTION:\n"
" -O: Enable OS detection (try 2nd generation, then 1st if that fails)\n"
" -O1: Only use the old (1st generation) OS detection system\n"
" -O2: Only use the new OS detection system (no fallback)\n"
" -O1: Only use the old (1st generation) OS detection system\n"
" --osscan-limit: Limit OS detection to promising targets\n"
" --osscan-guess: Guess OS more aggressively\n"
"TIMING AND PERFORMANCE:\n"

View File

@@ -31,7 +31,7 @@ web:
xnmap.1 nmap.usage.txt nmap.dtd nmap.xsl \
leet-nmap-ascii-art.txt $(wroot)/nmap/data/
cp $(wroot)/nmapguide/build/nmap-man.xml $(wroot)/nmap/data/nmap-man.xml
./sort-prints.pl ../nmap-os-fingerprints > nos && mv nos ../nmap-os-fingerprints
# ./sort-prints.pl ../nmap-os-fingerprints > nos && mv nos ../nmap-os-fingerprints
./produceosclasschoosebox.pl ../nmap-os-fingerprints > $(wroot)/nmap/data/os-classes.txt
cd .. && cp -a CHANGELOG HACKING COPYING COPYING.OpenSSL INSTALL \
$(DATAFILES) README-WIN32 mswin32/nmap_performance.reg $(wroot)/nmap/data