Talk:BitTorrent protocol encryption

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Protocol header encrypt[edit]

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.

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

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)

MikroTik[edit]

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.

Page move to "BitTorrent protocol encryption"[edit]

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)[reply]
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)[reply]
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)[reply]
Isn't that what we call IPSec? — ciphergoth 16:37, 24 March 2006 (UTC)

eMule[edit]

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)[reply]

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.

Would be nice to have details about this:

(e.g. pattern/timing analysis or categorizing ports based on side-channel data)

throttling and TOU[edit]

some ISPs have terms of use for residential broadband services that prohibit public content sharing directly from home computers rather than via the server based content sharing services provided by the ISP.

throttling can be used to enforce TOU as well as for bandwidth management. —Preceding unsigned comment added by 68.80.214.27 (talk) 23:49, 11 November 2007 (UTC)[reply]

Simple Details[edit]

So in plain English, does it reveal what is being transferred to anyone watching or not? —Preceding unsigned comment added by 207.172.90.28 (talk) 05:56, 12 February 2008 (UTC)[reply]

info hash - infohash[edit]

There are no current WP articles about "info hash", which is used with torrents. The passing mention in BitTorrent protocol encryption seems to be the only current content. There should be more user-relevant content along these lines:

"The info hash is strictly for the bittorrent client. The BT Client you use uses the info hash to make sure that what you are downloading is legit from the server's point of view. You don't do anything with it." -96.237.7.209 (talk) 13:51, 18 January 2009 (UTC)[reply]

Sentence on encryption methods does not make sense[edit]

It seems to me that the following sentence found in the security section of the page is malformed and also a run-on sentence: "AES was proposed as the encryption method but not adopted because it consumed too much CPU time and required Diffie–Hellman keys to achieve a security equal to AES would have been much bigger or require elliptic curve cryptography, making the handshake more expensive in terms of used CPU time."

I believe the sentence should be revised to the following: "AES was proposed as the encryption method but not adopted because it consumed too much CPU time. The required Diffie–Hellman keys to achieve a security equal to AES would have been much bigger or require elliptic curve cryptography, making the handshake more expensive in terms of used CPU time."

I will change it in a bit if no one objects.

--JetCrusherTorpedo (talk) 21:14, 12 November 2015 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on BitTorrent protocol encryption. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 21:12, 5 April 2017 (UTC)[reply]

BitTorrent/uT encryption and client-tracker traffic, Default (custom) DNS and client-tracker traffic[edit]

Apparently uTorrent doesn't encrypt client-tracker traffic(?) even when "full/force encryption" selected(?).

By default in uTorrent's extra settings primary & secondary DNS are to OpenDNS servers. Thus avoiding ISP's DNS.

Does client-tracker traffic also go default through OpenDNS? Or some other custom DNS provider the user has set up? CIRDUR (talk) 09:30, 20 April 2017 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified 5 external links on BitTorrent protocol encryption. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 03:48, 21 July 2017 (UTC)[reply]

Sandvine[edit]

I have removed a paragraph from the "Effectiveness" section that talked heavily about Sandvine, as it was uncited since 2012 and read like an advertisement for their products. Gsuberland (talk) 16:02, 3 April 2020 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:BitTorrent_protocol_encryption&oldid=1206315529"