nmap icon indicating copy to clipboard operation
nmap copied to clipboard

Ncat's proxy connect option should use Nsock proxychains

Open dmiller-nmap opened this issue 5 years ago • 2 comments

Ncat currently uses custom proxy connection code in ncat_connect.c. We should replace this with Nsock's proxychains support to keep all such code in one place. Some new features must be added, but we will get more features for Ncat in the process.

Things missing from Nsock that Ncat implements:

  1. Remote name resolution or connect-by-name for proxy types that allow this (HTTP and SOCKS 4a/5 allow these, but Nsock doesn't have a good way currently to handle it).

New features that Ncat will gain by this:

  1. Ability to chain more than one proxy.
  2. More transparent SSL connection capability (was entirely broken, and the fix to #2065 uses nsock_reconnect_ssl() with an IOD converted from a plain socket with nsock_iod_new2(), which the documentation says isn't really supported).

dmiller-nmap avatar Jun 17 '20 22:06 dmiller-nmap

AFAICT, proxy authentication and SOCKS5 support are also missing from Nsock but present in Ncat.

nnposter avatar Jun 27 '20 23:06 nnposter

I've just hit the bug in #2065 and after some searching landed here. Any plans to implement this?

digininja avatar Sep 17 '24 17:09 digininja