Socks client support #105
Open
Socks client support #105
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
|
I take it this was never merged? |
morckx
pushed a commit
to morckx/vxconnectbot
that referenced
this pull request
Sep 13, 2016
Update to library-based build
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I've basically made some simple changes that permit VX Connectbot to connect to SOCKS5 proxies. It uses the HTTP proxy configuration portion when you edit the host, and putting in a URL like socks5://my.socks.server:1080 (pre-patch this only permits HTTP proxies), you can use a SOCKS5 proxy to connect. I've used this to good effect connecting to some personal Tor hidden services with the help of Orbot. (socks5://127.0.0.1:9050 suffices for this).
I've needed to merge some of the jsocks upstream code in order to get this to work, and made a few changes to the trilead SSH code to make it use a SocksSocket instead of a plain socket, and to use SOCKS-based DNS resolution rather than local DNS.
This feature obviously requires a bit of cleanup before it's ready, but it's a start I think.