Nmap Development mailing list archives
Re: [NSE] comm.lua setup_connect should connect to host.ip in preference to host.targetname
From: jah <jah () zadkiel plus com>
Date: Mon, 05 Apr 2010 20:46:36 +0100
On 05/04/2010 18:47, David Fifield wrote:
The patch looks completely correct to me. You can commit it. As it is now, host.ip will always be available.
OK, done.
Not now. When proxy scanning is implemented, it could potentially be possible to scan a host only knowing its hostname, relying on the proxy to resolve the name. That may not happen, because the easier (less anonymous) approach would be for Nmap to resolve the name and pass the IP address to the proxy, plus not all proxy types support name resolution. Using the proxy to resolve names is interesting, because then you could use Nmap to port scan Tor .onion names.
This will be muy cool. It'll be an interesting discussion on how such a feature will affect NSE... Cheers David, jah _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [NSE] comm.lua setup_connect should connect to host.ip in preference to host.targetname jah (Apr 05)
- Re: [NSE] comm.lua setup_connect should connect to host.ip in preference to host.targetname David Fifield (Apr 05)
- Re: [NSE] comm.lua setup_connect should connect to host.ip in preference to host.targetname jah (Apr 05)
- Re: [NSE] comm.lua setup_connect should connect to host.ip in preference to host.targetname David Fifield (Apr 05)