ncat no resolves the desired endpoint in PROXY connections #1230
Assignees
Labels
Comments
|
Can you verify please? |
|
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. |
jaymzh
pushed a commit
to jaymzh/nmap
that referenced
this issue
Jun 11, 2018
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! |
|
Ability to control DNS resolution implemented in r37586. Thank you for raising up the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I spent a while git-bisecting this and it comes down to this commit:
21b7e38
Before this commit, if you did:
Then what was sent to MYPROXY was:
Where
2611:1a:e10::4is the IPv6 address of ENDPOINT.After this commit, this is sent:
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: