How to deal with Torrent poisoning ?

[neilwangweili]

In wikipedia, I found an entry to explain torrent poisoning's countermeasures.

The methods of attack described above are not particularly effective on their own, as for each measure effective countermeasures have evolved. These measures must be combined in order to have a significant impact on illegal peer-to-peer filesharing using BitTorrent protocols and Torrent files.

BitTorrent is highly resistant to content poisoning (as opposed to index poisoning), as it is able to verify individual file chunks.[12] Overall, BitTorrent is one of the most resistant P2P filesharing methods to poisoning.[7]
On private tracker websites, where all posted torrents can be traced to a particular member, poisoned torrents can be quickly labeled and deleted and the poster can be banned, preventing further introduction of poisoned torrents by that user.
Public torrent tracker sites have enabled the ability to report if a torrent has been poisoned (or is fake or malicious in any way). Thus torrent files shared by public trackers can have similar levels of quality assurance as Private Tracker websites.
Tracker technology (as well as BitTorrent client programs) has improved over time, and many kinds of spoofing that were possible in the past are no longer possible.
BitTorrent was once an exclusively TCP-IP protocol, but this is no longer true. Use of UDP, with the uTP protocol has made TCP Man in the Middle attacks more difficult to nearly impossible.
Public or Private tracker websites have selectively switched over to using HTTPS for the distribution of their web text and image content. By using HTTPS for the website content (versus tracker communications) many poisoning techniques are rendered impossible.

Is there an effective solution to this attack? Does peertube have any good precautions against this?

[rigelk]

hi @VWWL,

Since we rely on https://github.com/webtorrent/bittorrent-tracker, I guess this question is better suited for their issue tracker.