Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
I spent a while git-bisecting this and it comes down to this commit:
Before this commit, if you did:
./ncat/ncat --proxy-type http --proxy MYPROXY:8080 ENDPOINT
Then what was sent to MYPROXY was:
CONNECT [2611:1a:e10::4]:22 HTTP/1.0\r\n
Where 2611:1a:e10::4 is the IPv6 address of ENDPOINT.
After this commit, this is sent:
CONNECT ENDPOINT:22 HTTP/1.0\r\n
Which the proxy may not be able to resolve which causes a failed to resolve error, which then breaks being able to proxy.
The text was updated successfully, but these errors were encountered:
Can you verify please?
Sorry, something went wrong.
I'll give that a shot today, but I'm referring to HTTP proxy, not socks4 proxy, and that commit looks specific to socks4.
Yes, I see now. But the problem is pretty much the same. Will check if it can be fixed in same PR for http proxy as well
Thanks. Ping me again when the PR is updated, and I'll happily test.
[ncat] Fix v6 connectivity
When you pass in a v6 literal (to work around nmap#1230), you run into the problem
that ncat adds an extra square-bracket breaking the syntax.
Could you please take a look at #1439 and let me know if it would meet your needs?
commented on the PR, thanks!
Hi @nnposter ,
#1439 looks good. Thanks!
Ability to control DNS resolution implemented in r37586. Thank you for raising up the issue.
Successfully merging a pull request may close this issue.