Re: [NSE] scan traceroute hops

[Djalal Harouni <tixxdz () gmail com>]

On 2010-09-08 09:29:50 +0200, Henri Doreau wrote:
> Hi,
>
> thank you for the precision. What bothered me, or at least raised my
> attention, is the fact the target is added the first time, even if it
> is already in the scanning queue because specified in the command
> line. Maybe this case worth being checked and reported to the user?
Currently Nmap do not save scanned targets (only NSE added targets are
saved), but if we want to filter all targets we should provide a good
solution. I hope that I'll have some time in the future to look at it
and any help is welcome.

I've changed the target.add() function internals to return non-zero
value if the target is already in the queue. I think that most of the
scripts will not care about this, and they only want to push new
targets. However I'll try to add some NSEdoc to the target.add() function
to make it clear.

Thx.

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