(untitled)

how does qbittorrent encryption work? does it encrypt all traffic so that the isp doesn't know what your are downloading?

>>73393 Most questions can be answered here: https://www.bittorrent.org If we go to this page, we find the part on encryption: https://www.bittorrent.org/beps/bep_1000.html However, standard 13 doesn't exist on the website. Now, I know Wikipedia to be a cesspit, but a simple WWW search leads me there first, and Wikipedia is at least useful for collecting sources, sometimes. I found this: https://torrentfreak.com/interview-with-bram-cohen-the-inventor-of-bittorrent/ I've read elsewhere that BitTorrent encryption is fake encryption and doesn't actually do anything useful. Well, the creator of BitTorrent states that right here: >TorrentFreak: The mainline client now supports encryption, but there are no settings to control this (correct me if I’m wrong). Does this mean that the client encrypts all transfers? >Bram Cohen: No. The mainline client accepts incoming encrypted connections, but makes unencrypted outgoing connections by default. We added support for that primarily for our users in unfriendly ISP environments. As I’ve said before, protocol encryption is at best a temporary hack around ISP rate limiting, until identification techniques are put in place which use transfer patterns rather than packet inspection to identify traffic. There are better approaches to evade traffic shaping, although we’re still trying to work productively with ISPs, who own the network after all. But if we can’t find a way to work together to provide a better experience for BitTorrent users, then the arms race will begin. >TorrentFreak: You said before that you’re not a big fan of encryption. What would you suggest as an alternative? >Bram Cohen: I say just leave things in the clear, and try to use caching technology to improve the ISP network. Or better yet, ISPs should lay more fiber and build bigger pipes. >The so-called ‘encryption’ of BitTorrent traffic isn’t really encryption, it’s obfuscation. It provides no anonymity whatsoever, and only temporarily evades traffic shaping. There are better approaches to obfuscation, and I’ve got a great team of engineers who are quite eager to fight that battle, but I’m hoping that everything can be resolved amicably without getting into a serious arms race. So there we have it.

https://en.wikipedia.org/wiki/BitTorrent_protocol_encryption It uses RC4 so consider it obfuscation rather than proper encryption. Also: > Analysis of the BitTorrent protocol encryption (a.k.a. MSE) has shown that statistical measurements of packet sizes and packet directions of the first 100 packets in a TCP session can be used to identify the obfuscated protocol with over 96% accuracy.

On top of the RC4 encryption algorithm being almost completely broken, you're going to be connecting to trackers for your torrents over unencrypted connections anyways and the same goes for DHT (and probably PeX) being unencrypted. So you'll need to use a VPN. But your ISP isn't really what you should be worried about anyways, it's the anti-piracy organizations that connect to swarms and send out automated threatening letters to people downloading copyrighted stuff on behalf of rightsholders. If you receive enough of these letters your ISP may cut off your internet depending on which company they are. Just buy Mullvad VPN since it's the most private option, turn on the internet kill switch so traffic doesn't leak if the VPN disconnects, and never worry about any of this. There are also cheaper no-logs VPNs out there if the price is too high and you probably won't realistically be losing any privacy going with those other options. https://www.privacyguides.org/en/vpn/

>>73455 Mullvad isn't very good for torrenting because of it not allowing port forwarding anymore. Airvpn is better imo

>>73459 personally any vpn that allows you to pay with monero is good enough to me. i dont use port forwarding anyways.