EXPERIMENTAL: Reduce Tor Circuits Created Client Side from 3 Hops to 2 Hops #21
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.
DANGER: This commit compromises the security of Tor by completely eliminating the Middle Tor Nodes. It is not recommended to use this without a VPN or another form of anonymisation.
This commit modifies the source code of Tor to reduce the nodes used when creating the circuits from 3 to 2. Unfortunately attempting to reduce this to 1 did not work as most Tor nodes completely reject traffic using Single Node traffic.
Notably when applying the patch the download speed is more stable in comparison to using 3 nodes but please feel free to test this and give feedback before merging.
Note .onion sites typically use a total of 6 hops - 3 client and 3 server. With this commit it reduces it to 5 hops due to 2 client and 3 server.