Re: top-ports range

[Daniel Miller <bonsaiviking () gmail com>]

Toni, David,

The use of -p with --top-ports is supported, since it's what I took
advantage of for this perl-based workaround to the lack of an
--exclude-ports option: http://seclists.org/nmap-dev/2012/q2/159

The way it currently works is: -p specifies a set of ports, and
--top-ports specifies how many of the most popular ports in that set
get scanned. So -p 80,443,1234 --top-ports 2 would scan only 80 and
443. It's not likely many people are relying on this behavior, but
it's important to note that it exists.

Dan

On Wed, Jul 25, 2012 at 1:21 AM, Toni Ruottu <toni.ruottu () iki fi> wrote:
> Ok. So two distinct feature requests. 1) union between -p and
> --top-ports, and 2) range support for --top-ports. Would one of the
> GSoC folks be willing to look at one or the other? This is not a high
> priority, but the tasks might not be that hard either.
>
> On Wed, Jul 25, 2012 at 9:01 AM, David Fifield <david () bamsoftware com> wrote:
> > There's special logic that cheats and puts common ports like 80 at the
> > front of the list (random_port_cheat in portlist.cc). But unfortunately
> > it still won't work because you can't use -p and --top-ports together.
> > (I think you should be able to, and it should take the union.)
> >
> > 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/
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/