SOCKS5 layer#318
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR introduces a SOCKS5 proxy transport. Now you can use Unbounded anywhere you can use a SOCKS5 proxy.
Context:
The Unbounded protocol does not specify an end-to-end proxy protocol. Rather, the Unbounded protocol simply specifies a multiplexed stream oriented tunnel -- which happens to be a peer-to-peer tunnel over ephemeral volunteer transports -- that can move bytes from one place to another. If you want to actually proxy those bytes, you need to bolt a chained proxy protocol over the tunnel.
Historically, we've bolted an HTTP proxy over the Unbounded tunnel, and that's how we've used Unbounded as part of our censorship circumvention stack. Unbounded ships with an HTTP transport for this purpose.
Now Unbounded also ships with a SOCKS5 transport. Specifically, a SOCKS5 transport that works well with
armon/go-socks5. But it would be relatively trivial to port the transport to other SOCKS5 servers.