The protocol is more or less all plaintext. The "best" peer to peer cipher available is rc4; almost no one uses it. The tracker announces can run over HTTPS, but often run over plain HTTP.
The "best" peer to peer cipher available is rc4; almost no one uses it.
...which is unfortunate because even something like the anonymous DH that is specified, or more standard, TLS with random/self-signed certificates, would force monitors to need to MITM all connections in order to find out what they contain.
Because, quite frankly, parts identified by hashes is not all they see.
If you're monitoring and logging the traffic then it's trivial to not only determine the filename of a bittorrent download, but also everything you need to connect to the torrent yourself and download it to verify that it's what the filename says, if that's what you wish to do.
And, personally, I'd expect someone to at least check the filename before accusing me of committing a crime. :(
The torrent file is downloaded over a secure connection that you can’t monitor. Can you please tell me which messages in the BitTorrent protocol contain the filenames?
