Nmap Development mailing list archives
Re: Possible regression: weird IPv6 error when trying to portscan behind proxychains
From: Daniel Miller <bonsaiviking () gmail com>
Date: Mon, 13 Oct 2014 13:01:40 -0500
On Sat, Mar 29, 2014 at 12:42 PM, Jacek Wielemborek <d33tah () gmail com> wrote:
root@linux-pc:~# proxychains nmap -sV scame.nmap.org ProxyChains-3.1 (http://proxychains.sf.net) Starting Nmap 6.41SVN ( http://nmap.org ) at 2013-09-22 00:31 AST |DNS-request| scame.nmap.org |S-chain|-<>-127.0.0.1:9050-<><>-4.2.2.2:53-<><>-OK |DNS-response| scame.nmap.org is 173.255.243.189 173.255.243.189/0 looks like an IPv6 target specification -- you have to use the -6 option. WARNING: No targets were specified, so 0 hosts scanned. Nmap done: 0 IP addresses (0 hosts up) scanned in 1.56 seconds (original source: http://paste.ubuntu.com/6138529/)Just wanted to let you know that this bug still affects current SVN.
I took some time today to track this down. Turns out it's a problem with proxychains not respecting the AI_NUMERICHOST flag to getaddrinfo. Proxychains-ng fixed this in 4.8: Version 4.8: - fix for odd cornercase where getaddrinfo was used with AI_NUMERICHOST to test for a numeric ip instead of resolving it (fixes nmap). Since proxychains was last updated in 2006, I suppose proxychains-ng is the way to go. Dan _______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Re: Possible regression: weird IPv6 error when trying to portscan behind proxychains Daniel Miller (Oct 13)