Added ability to use socks proxy for server/client communication #410
+89
−6
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
|
HI, any updates on this? I've been trying to do something similar. I see the ci build failed but you claim you have tested it locally? Thanks. |
|
@leocornelius Yes, it's working. You can use my forked version pusblished on NPM here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 adds ability to connect to localtunnel server via socks proxy (using Tor for example) thus adding ability to hide real IP address of the client from the server. This is especially useful for people running their own localtunnel server instances because it allows their users to protect against revealing their real IP (and deanonymize them) by a malicious actor. Therefore it makes this service more trustless.
I've tested this locally using default localtunnel server.