Nmap Development mailing list archives
[ncat][RFC] Ability to control hostname resolution for proxy destinations
From: nnposter <nnposter () users sourceforge net>
Date: Tue, 22 Jan 2019 14:06:07 -0700
In connect mode, currently all proxy destinations are directly passed onto the remote proxy server, without trying to resolve them locally. This behavior has raised some concerns.
I am proposing a new ncat option that provides control over whether these hostnames are resolved by the remote proxy server or locally, by Ncat itself.
Usage: ncat ... --proxy-dns local | remote | both | none More at https://github.com/nmap/nmap/pull/1439 Please review the proposal and comment. Cheers, nnposter _______________________________________________ Sent through the dev mailing list https://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- [ncat][RFC] Ability to control hostname resolution for proxy destinations nnposter (Jan 22)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy destinations David Fifield (Jan 23)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy nnposter (Jan 25)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy David Fifield (Jan 25)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy nnposter (Jan 25)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy nnposter (Jan 25)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy destinations David Fifield (Jan 23)
- Re: [ncat][RFC] Ability to control hostname resolution for proxy nnposter (Feb 20)