Suspect that --host-timeout is not working in 4.50?

[Randolph Reitz <rreitz () fnal gov>]

Hi,

I have installed nmap 4.50 on the scanner farm here at Fermilab and  
I've noticed that some nmap scans are running a long time.  For  
example ...

scanner   5311 31009  0 12:17 ?        00:00:00 /bin/bash ./bin/ 
run_nmap.sh --pro -d 1 -sS -p 1-65535 -A 131.225.232.A 131.225.232.B  
131.225.232.C 131.225.232.D
root      5319  5311  2 12:17 ?        00:03:10 /usr/local/bin/nmap - 
sS -p 1-65535 -P0 -T4 --osscan-limit --osscan-guess --host-timeout 15m  
-A -oX - 131.225.232.D

It's now
date
Fri Dec 14 14:47:47 CST 2007

The nmap started at 12:17 and has collected 3 minutes of CPU so far.   
The host_timeout is set for 15 minutes.  So far, I've collected  
hundreds of examples of long-running nmap scans.  However, I've  
noticed that nmap 4.50 is much faster than 4.2.

Does anyone else have a problem with --host-timeout?

I have made a feeble attempt to obscure the IP addresses.

Thanks,
Randy Reitz
Fermilab


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org