Talk:BitTorrent protocol encryption

From Wikipedia, the free encyclopedia

Contents 1 Protocol header encrypt 2 remove "This article documents a current event" 3 MikroTik 4 Page move to "BitTorrent protocol encryption" 5 eMule

[edit] Protocol header encrypt

Protocol header encrypt is bad grammar but that's what BitComet calls it. WP 08:51, 5 February 2006 (UTC)

The abbreviation PHE is used outside the BitComet area too (mostly by users of other clients that heared about the future), but then it's usually expanded to encryption and not encrypt, i think we should point that out in the article and only mention the "official" expansion in the article header and then use encryption. That sounds better and is grammatically correct.

[edit] remove "This article documents a current event"

Can I recommend removal of "This article documents a current event" tag, as I don't believe it is a fast changing event (not like top news stories for eample)

OK.WP 08:31, 18 February 2006 (UTC)

[edit] MikroTik

Right now only the MikroTik RouterOS routing system can successfully detect encrypted BitTorrent traffic (by Azureus) and deal with it from within it's firewall.

An anon using an IP from Riga, Latvia posted the above about a router produced in Riga, Latvia without citing sources. If anyone could find a source for the above that would be great. WP 05:55, 25 February 2006 (UTC)

See [1]. In addition that he removed his µT mention it makes this claim highly improbable unless it's referring to plain transmission mode only. Another issue is the 'Right now' part seems to be a claim that's not easy to prove, thus i suggest removing this section and will do that if nobody vetos. And i've checked their QoS chapter... it seems that they're using the usual iptables (netfilter)/tc combination, which isn't capable of identifying fully encrypted connections atm. But plain ones are easy to identify, but that's possible with every iptables implementation... no "special" hardware is necessary for that.

[edit] Page move to "BitTorrent protocol encryption"

All encryption is part of a cryptographic protocol - the title should reflect what the article is really about I think. Will move in a bit if no-one shouts. — ciphergoth 07:31, 12 March 2006 (UTC)

Maybe "Message stream encryption"? That's the name of the official specs. But people usually use "protocol encryption" instead of MSE. WP 07:54, 12 March 2006 (UTC)

The encryption protocol is designed to be a wrapper protocol, independent of the encapsulated protocol. So it's not Bittorrent-specific and the move unjustified! —The preceding unsigned comment was added by 134.108.34.9 (talk • contribs) 13:17, 20 March 2006 (UTC)

Are there any non-trivial users besides BitTorrent? — Matt Crypto 12:22, 20 March 2006 (UTC)

Currently there aren't. But that doesn't change that this protocol isn't bt-specific... I'll have a look at the naming policy, maybe it has some rules for that fit this case. --134.108.34.9 09:18, 22 March 2006 (UTC)

Isn't that what we call IPSec? — ciphergoth 16:37, 24 March 2006 (UTC)

[edit] eMule

As of 0.47b/c emule also uses protocol encyption. It is called porotcol obfuscation here however since encryption assumes no-one is able to break the communication. THis is hoever not thrue because the encryption is just good enough to prevent routers to detect the traffic type without doing some heavy computations. anyone wanting to break the encryption can do because there is a shared secret that can be obtained by joining the network. More: http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=848

maybe someone want to add this to the article, Did not add it since it was moved to "bittorrent bla bla"and not the general protocol encrption. :Leuk he 09:14, 25 September 2006 (UTC)

since encryption assumes no-one is able to break the communication that's not entirely correct. Encryption is just a tool. Which guarantees are tried to make (authentication, integrity checking, secrecy, deniability etc.) depends on the implementing protocol.