Re: top-ports range

[Toni Ruottu <toni.ruottu () iki fi>]

Maybe I could do "-p 80 --top-ports 11-20" if I knew port 80 was open.
However I guess port 80 might accidentally be scanned last in which
case it does not help.

On Mon, Jul 23, 2012 at 6:08 PM, David Fifield <david () bamsoftware com> wrote:
> On Mon, Jul 23, 2012 at 11:58:29AM +0300, Toni Ruottu wrote:
> >   Good day, list!
> >
> > After doing a scan with "--top-ports 10" I would want to proceed with
> > another scan to get results for the following 10 ports when ordered by
> > popularity (i.e. "--top-ports 11-20"). Does this functionality already
> > exist in some form, or would it be a reasonable addition?
>
> It's a pretty reasonable idea. The ability to do this might not always
> save time though. It's likely that --top-ports 1-20 will be faster than
> --top-ports 11-20, because the first will probably find ports that it
> can use for timing pings.
>
> David Fifield
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/