Nmap Development mailing list archives
Re: [nmap-svn] r26641 - nmap
From: Fyodor <fyodor () insecure org>
Date: Sat, 8 Oct 2011 00:38:38 -0700
On Thu, Oct 06, 2011 at 10:03:48AM -0700, David Fifield wrote:
On Thu, Oct 06, 2011 at 01:05:15PM +0300, Toni Ruottu wrote: For what it's worth I think Nmap should be able to handle IPv4 and IPv6 in a single invocation.
Yes, that would be nice!
The only question is what to do in this case: nmap 192.0.43.10 scanme.nmap.org 2001:500:88:200::10 Should scanme.nmap.org be resolved as IPv4 or IPv6? Some options are 1) Always preferentially use IPv4. 2) Always preferentially use IPv6. 3) Use the getaddrinfo policy.
Good points. Another option would be to scan both. At least our resolveall.nse could be agumented to do so. Though I think that functionality would be welcome as an official Nmap option at some point. Resolveall.nse is great, but it requires a pretty awkward syntax (--script=resolveall --script-args=newtargets,resolveall.hosts={<host1>, ...}) compared to a plain Nmap option. Cheers, Fyodor _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: [nmap-svn] r26641 - nmap Fyodor (Oct 05)
- Re: [nmap-svn] r26641 - nmap Toni Ruottu (Oct 06)
- Re: [nmap-svn] r26641 - nmap David Fifield (Oct 06)
- Re: [nmap-svn] r26641 - nmap Fyodor (Oct 08)
- Re: [nmap-svn] r26641 - nmap David Fifield (Oct 06)
- Re: [nmap-svn] r26641 - nmap Toni Ruottu (Oct 06)