Re: CIDR range capabilities for ipOps (NSE Leftovers - Part 3)

[Brendan Byrd <sineswiper () gmail com>]

> I still find it hard to see what is going on here. This is partly
> because it seems to contain a whole lot of unrealted stylistic changes,
> for example
> -  elseif ip:sub(1,3) == '10.' then
> +  elseif sub(ip,1,3) == '10.' then
> Maybe you made the patch against an old version of the library or
> something? At any rate, please remove all those changes if you want the
> patch to be considered.

I think this was a case of seeing a consistency problem and trying to
fix it, as I remember seeing it both ways.  Which form is "correct"?

> What is a specific use case for this CIDR range capability? How do you
> see it being used in a script? Is it necessary for the SNMP changes you
> earlier proposed?

A lot of it is connected, yes.  This is used by both the target
library changes and the new snmp-routing script.  Besides, since nmap
deals a lot with IP ranges, there should be some scripting code to go
along with it.

-- 
Brendan Byrd/SineSwiper <SineSwiper () GMail com>
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/