BitTorrent protocol encryption: Difference between revisions

Revision as of 04:36, 13 February 2006

Revision as of 04:40, 13 February 2006

Line 12:

Azureus supports the final spec since [[25 January]] [[2006]] (CVS snapshot 2307-B33) [http://sourceforge.net/mailarchive/message.php?msg_id=14596518] and µTorrent followed 4 days later with beta 1.4.1 build 407. [http://forum.utorrent.com/viewtopic.php?id=5384] The new protocol is called MSE in Azureus and PE in µTorrent.

Azureus version 2.4.0.0 was released February 10th, 2006. This is the first full release version of a client to support the encryption. The choice between header & stream encryption has been removed. Azureus implements full stream encryption as does µTorrent.

[[Bram Cohen]], the inventor of [[BitTorrent]], recently commented disfavouring on the ongoing development to obfuscate the BitTorrent protocol. [http://bramcohen.livejournal.com/29886.html] Encrypted BitTorrent users quickly pointed out flaws in his reasoning. [http://forum.utorrent.com/viewtopic.php?id=5742]

Line 22:

The specification allows the users to choose between encrypting the headers only or the full connection. Encrypting the full connection provides more obfuscation but uses more CPU time. However, PE in µTorrent beta 1.4.1 build 417 or later only supports full encryption for outgoing connections, but will accept both obfuscation levels for incoming connections.

In the full release versions the choice between header & stream encryption has been removed. Both Azureus & µTorrent implement full stream encryption.

To ensure compatibility with other clients that don't support this specification users may also choose whether unencrypted incoming or outgoing connections are still allowed.