This repository has been archived by the owner on Oct 10, 2019. It is now read-only.
add support for the socks5h proxy type #452
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The proxy type socks5h does the hostname resolution on the proxy instead of the client (hence the name) and is therefore preferred with e.g Tor. The socks5 type allows a client to do either with most performing the DNS lookup locally and asking the socks5-proxy server to connect to a specific IPv4/6. That can fail if the server has another network setup – like no IPv6 – and in terms of Tor it means that DNS queries are leaked and .onion addresses aren't working.
|
Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The proxy type socks5h does the hostname resolution on the proxy instead
of the client (hence the name) and is therefore preferred with e.g Tor.
The socks5 type allows a client to do either with most performing the
DNS lookup locally and asking the socks5-proxy server to connect to a
specific IPv4/6. That can fail if the server has another network setup –
like no IPv6 – and in terms of Tor it means that DNS queries are leaked
and .onion addresses aren't working.