Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tor stream isolation support #266

Open
1cho1ce opened this issue Nov 5, 2023 · 1 comment · May be fixed by #271
Open

Tor stream isolation support #266

1cho1ce opened this issue Nov 5, 2023 · 1 comment · May be fixed by #271

Comments

@1cho1ce
Copy link

1cho1ce commented Nov 5, 2023

Right now if hydroxide has multiple accounts then connection to all of them will go through the same Tor circuit and it'll cause identity correlation. Using HTTPS_PROXY or torsocks won't help here and stream isolation should be implemented inside hydroxide so all new connections will use a fresh circuit, rather than possibly re-using an existing circuit.
This could be implemented using this package when hydroxide is started with -tor 127.0.0.1:9050 option:
https://pkg.go.dev/github.com/lightningnetwork/lnd/tor

@h3xagonal h3xagonal linked a pull request Apr 7, 2024 that will close this issue
@emersion
Copy link
Owner

emersion commented May 8, 2024

I don't believe plumbing Tor/proxy support to each and every program that uses TCP is a good way forward. I would recommend setting up a system-wide transparent proxy instead (TransPort in Tor config), which makes Tor work similarly to VPNs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants