Nmap Development mailing list archives

Re: [nmap-svn] r12219 - nmap-exp/david/ncat-allowdeny/test


From: David Fifield <david () bamsoftware com>
Date: Fri, 20 Feb 2009 21:24:40 -0700

On Fri, Feb 20, 2009 at 02:38:29PM -0800, Fyodor wrote:
On Fri, Feb 20, 2009 at 09:01:00AM -0800, commit-mailer () insecure org wrote:
The specifications "1", "1.2", and "1.2.3" are interpreted as 0.0.0.1,
1.0.0.2, and 1.2.0.3 respectively. That's surprising, but it's how ping
and my web browser interpret the addresses, so Ncat should do the same.

In my opinion, we don't need to go to any extra effort or code
complexity to make those perverse IP specifiers work.  Unless people
actually do that on purpose (anyone here?), I think a failure to parse
error would be better.  Because it probably means they accidentally
left off an octet.

There's no extra effort; it's what naturally falls out of getaddrinfo.
It would take extra work to prohibit them, but I could do it. I
explicitly commented out those tests in test-addrset.sh to show that it
wasn't required behavior.

David Fifield

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


Current thread: