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

In theory: webtorrent and tor #1066

Closed
fsteff opened this issue Mar 1, 2017 · 2 comments
Closed

In theory: webtorrent and tor #1066

fsteff opened this issue Mar 1, 2017 · 2 comments

Comments

@fsteff
Copy link

@fsteff fsteff commented Mar 1, 2017

I recently read this article: https://blog.torproject.org/blog/bittorrent-over-tor-isnt-good-idea and I asked myself if this also applies to webtorrent.

In short: Bittorrent and tor are a bad combination because a) the tracker needs (and distributes) your real IP and b) the bittorrent protocol uses UDP, which is not supported by tor.
(I am not talking about the tor browser bundle, which does not support WebRTC and blocks javascript per default - rather using tor as a proxy in general)

I am no expert with WebRTC so I´m asking you if these arguments also apply to webtorrent.
Privacy is a major problem, especially when a website uses it to distribute the server load - everybody can see who is visiting the website. This actually is a reason for me not to use it at all in websites.
(similar: #788)

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Mar 1, 2017

WebRTC can connect over UDP or TCP, so I believe that TCP would be used if all your traffic was being tunneled over a Tor proxy.

But I'm not actually whether STUN would be supported over Tor. I thought they used UDP, but apparently they can also be sent over TCP. Unsure if browsers support that, but it's worth investigating further.

If all your traffic is set up to go through the Tor proxy then I believe you're safe, since you're never talking directly to the internet. But if STUN packets require UDP in current browsers, then I bet that WebRTC connections wouldn't work at all.

Only one way to find out!

@feross feross closed this Mar 1, 2017
@lock

This comment has been minimized.

Copy link

@lock lock bot commented May 3, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.