Re: [ncat][RFC] Ability to control hostname resolution for proxy
nnposter <[email protected]> Fri, 25 Jan 2019 09:57:03 -0700
| Newsgroups | gmane.comp.security.nmap.devel |
|---|---|
| Message-ID | <[email protected]> |
On 1/24/19 12:13 AM, David Fifield wrote: > On Tue, Jan 22, 2019 at 02:06:07PM -0700, nnposter wrote: >> >> ncat ... --proxy-dns local | remote | both | none >> >> More at https://github.com/nmap/nmap/pull/1439 >> Please review the proposal and comment. > > curl uses different URL schemes to control whether name resolution is > local or remote: https://curl.haxx.se/docs/manpage.html#-x > socks4, socks5: local > socks4a, socks5h: remote > > But personally I've never liked that setup. I almost always want remote > resolution and have to remind myself not to use the versions that will > leak DNS. And of course it doesn't work for http or https proxies. I agree. It is definitely overloading the concept of a protocol. Back to my proposal, what would be your vote? (1) ignore; do nothing (2) proceed with it (3) the feature should be somehow supported but not this way Cheers, nnposter _______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/