[tor-relays] Request for Tor abuse complaints - Question regarding Bittorrent

[Tristan]

I've tested many torrent clients with Tor's proxy. Vuze is the only one
that strictly follows the settings, every other client ignores the proxy if
it fails.

In Vuze, most trackers failed to connect, but with DHT (not sure if DHT
goes through the proxy) the actual torrent still goes through Tor.

Honestly I'm not sure how torrent clients would grab Tor IPs since
Wireshark shows it bypassing the proxy, but the check my torrent IP website
will show your proxy IP.

My guess is that whoever sends the DMCA just doesn't take the time to find
the real IP. For my part, BitTorrent ports are blocked on my exit, and I
never use torrents over Tor.

On Sep 29, 2016 7:09 AM, "Corné Oppelaar" <hello at eaterofco.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> This is because they scrape tracker's for peers and use this evidence
> to send complaints to the ips of the peers.
>
> trackers are in most cases reachable via http so they go over tor
>
> and then we exit operators are getting harassed :s
>
> On 09/29/2016 02:05 PM, janulrich wrote:
> >
> >
> > Sadia Afroz:
> >> We are researchers from Univ. of California, Berkeley and Univ.
> >> of Massachusetts Amherst are interested in understanding what
> >> kind of abuse happens through Tor.  Thanks to Moritz Bartl from
> >> Torservers.net <http://torservers.net/> we analyzed over 1GB of
> >> complaints received over 6 years. Here is our preliminary
> >> analysis of the complaints:
> >> http://www1.icsi.berkeley.edu/~sadia/tor_abuse_complaints.pdf
> >> <http://www1.icsi.berkeley.edu/~sadia/tor_abuse_complaints.pdf>
> >
> > Quote from paper:
> >> 99% are DMCA complaints regarding the use of bittorrent.
> >
> > Why do these complaints go to the exit node operators? Isn't the
> > complainer able to figure out the real IP of Bittorrent clients?
> >
> > Why I am asking this: torrent uses UDP, Tor only routes TCP
> > traffic. Isn't it impossible to hide bittorrent traffic via Tor.
> > _______________________________________________ tor-relays mailing
> > list tor-relays at lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
> -----BEGIN PGP SIGNATURE-----
>
> iQEcBAEBCAAGBQJX7QRGAAoJEE6fMe4ysJ7Mx8sIAIQSXt0XPqA5t4G0piqzaUWy
> ugtECy4tnRIL7zdJE3gjY0aWjsh3p+XsRZZXwh2+krV0LCvGjlEHs6g9AimRzCmX
> fv3maW9uoUx/SAzZasz3GI5QjnNsMbvgJN8Fvo0Oi8A3vEFYwZ0ypt/PFKP2Yr7v
> RvMt8d3WwFPHSFNaE6A9iLCyWvTbRmusdMhuMngUmg/+LLCTL9UFbvYNgUGZRg2u
> nVWW/6M0d/Tyg2jHGKgL1lbzOMmCAWgs4AaB5sQai4EbUxSMNp/EYz3uypsTASKF
> ZK3S54qbdBWDYnxJoJDyPJz5ZxBWkdn0E6gOCMWuQ3UoyH0zyTURSm8kjez3838=
> =6Kte
> -----END PGP SIGNATURE-----
> _______________________________________________
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160929/653b4c85/attachment.html>