BitTorrent protocol encryption: Difference between revisions

Revision as of 22:00, 26 January 2006

Revision as of 01:04, 27 January 2006

Line 1:

{{Current}}

'''Protocol header encrypt''' ('''PHE'''), '''Message stream encryption''' ('''MSE'''), '''Protocol encryption''' (PE) or '''Protocol header encryption''' ('''PHE''') are features of some [[BitTorrent]] clients that attempts to make BitTorrent hard to throttle. Some [[Internet service provider|ISP]]s throttle BitTorrent traffic because it makes up a large porportion of total traffic and the ISPs don't want to spend money buying extra capacity. Instead, the ISPs spend money on hardware that look for BitTorrent traffic and slow them down.

==History==

Protocol header encrypt was conceived by [[RnySmile]] and first implemented in the [[BitComet]] client version 0.60 on [[8 September]] [[2005]].

Line 7:

[http://sourceforge.net/mailarchive/forum.php?thread_id=9517694&forum_id=40629]

[[µTorrent]] will implement Protocol headerprotocol encryption in a later release. [http://forum.utorrent.com/viewtopic.php?pid=44229#p44229] It is not called protocol header encryption because it encrypts all of the data, not just the headers. Due to a lack of cooperation between the Azureus and µTorrent developers, µTorrent was planning to use its own protocol. However, recent developments may mean they will colaboratecollaborate on the protocol after all. [http://forum.utorrent.com/viewtopic.php?pid=45927#p45927] A new protocol specification was created by various developers and it was agreed that it was better than the current one in Azureus. Because of this, both clients are more than likely to implement the same new encryption protocol.

==Operation==