better access to nmap data from the NSE

["Robert Seger" <aframebug () gmail com>]

So far as I can tell, one doesn't have very good access to nmap's internal
data from an NSE script. For example, one isn't able to determine the number
of hosts that have been scanned (or the total that will be eventually).
Allowing access to this data is probably fairly annoying, but with it the
flexibility of the NSE would be greatly increased.

With access to the number of hosts that have been scanned, and the total
number to be scanned, one could very easily create a script that would only
be run after all hosts have been scanned. Add access to traceroute data,
when applicable, and one could create a script to identify likely VM-hosts
and/or machines simply answering more often than they should be.

How hard would it be to allow ful access to nmap's internal data from an NSE
script anyway?

Robert

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