[NSE] Target time out checks

["Patrick Donnelly" <batrick.donnelly () gmail com>]

Currently NSE starts the time out clock for all the hosts in a
runlevel group before beginning the scan. If there is an extremely
large group, some hosts may not be handled before a script thread is
mistakenly timed out (even when it has no connections open). Also, a
script may not actually be accessing that host at the time (whois.nse
will query the whois databse, not the target!!). For this reason, I do
not believe that the Target.timedOut method is appropriate for the
Script Engine. However, the target.startTimeOutClock and
target.stopTimeOutClock methods are still useful for tracking the
length of time the host was scanned (even if indirectly).

I have attached a patch that removes the checks to see if the target
host has timed out. If there are no complaints/problems/concerns I
will apply this in a couple days.

Cheers,

-- 
-Patrick Donnelly

"One of the lessons of history is that nothing is often a good thing
to do and always a clever thing to say."

-Will Durant

Attachment: nse_timeout.patch
Description:

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