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

WebTorrent's approach to user identification #1555

Closed
umaar opened this issue Nov 30, 2018 · 3 comments
Closed

WebTorrent's approach to user identification #1555

umaar opened this issue Nov 30, 2018 · 3 comments
Labels

Comments

@umaar
Copy link

@umaar umaar commented Nov 30, 2018

There was an issue raised some time ago where a law firm were asking WebTorrent for assistance in collecting the IP addresses of those who download their customers movies. It appeared the first reply, a WebTorrent contributor, was happy to assist further suggesting the law firm emails them directly.

image

Could you shed any light on this from a privacy perspective?

  • Does WebTorrent assist individuals and organisations who wish to track torrent downloaders/sharers?
@SilentBot1 SilentBot1 added the question label Nov 30, 2018
@SilentBot1

This comment has been minimized.

Copy link
Member

@SilentBot1 SilentBot1 commented Nov 30, 2018

Hey @umaar,

The only communication I have had with legallaw was in the GitHub issue you're referencing. I haven't had any further contact, outside of publicly in that issue on GitHub, with legallaw or any other law firm regarding WebTorrent.

As WebTorrent is a JavaScript implementation of the BitTorrent protocol, there exists the same privacy concerns in WebTorrent that exist with BitTorrent protocol. Without knowing the infohash or owning the tracker, there is no way to gather information about peers of a torrent. If you know the infohash then it's another story and it's trivial to query trackers for a list of peers, as this is required for the BitTorrent protocol to function. One solution to this is private trackers.

There are three default WSS trackers and, I believe, their respective maintainers are:

wss://tracker.btorrent.xyz - @DiegoRBaquero
wss://tracker.openwebtorrent.com - @alxhotel
wss://tracker.fastcast.nz - @jakefb

The source code for all three trackers are public.

As a organisation, I haven't seen any other members directly offer to aid somebody in achieving this. Personally I was more interested in discussing the feasibility of implementing this, rather than actually helping implement a solution. I wanted to better understand the possibilities and implications they pose to everybody using the WebTorrent library.

The WebTorrent project and contributors don't condone or support using WebTorrent for copyright infringement, this policy has been stated by Feross since as early as March 2015.

Because this isn't a issue, I'm going to close mark this as closed, though I'm more than happy to answer any further questions.

@SilentBot1 SilentBot1 closed this Nov 30, 2018
@jimmywarting

This comment has been minimized.

Copy link
Contributor

@jimmywarting jimmywarting commented Nov 30, 2018

If you as a peer manage to give out metadata using
Bep 9 - Extension for Peers to Send Metadata Files or
Bep 28 - Tracker exchange extension
to tell someone to use one of there own wss tracker you will be connected to that and start sharing your upload/download progress with announce requests

you can also see which has downloaded the hole file

And if the connection is TURN based you won't get his real ip adress

@umaar

This comment has been minimized.

Copy link
Author

@umaar umaar commented Nov 30, 2018

Hey @SilentBot1 - really appreciate your detailed response. Your thoughts/statements on WebTorrent is great to hear and is exactly what I was trying to understand more about.

Thanks for taking the time to explain!

@lock lock bot locked as resolved and limited conversation to collaborators Feb 28, 2019
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
3 participants
You can’t perform that action at this time.