Editing Protocol obfuscation
From EMule Wiki
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to cut-n-paste the text into a text file and save it for later.
The administrator who locked it offered this explanation: site maintenance
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Some providers are throttling eMule traffic (decreasing the allowed bandwidth). They do this by detecting the eMule protocol and allowing a very limited amount of the total bandwidth to be used by eMule. | + | Some providers are throttling eMule traffic (decreasing the allowed bandwidth). They do this by detecting the eMule protocol and allowing a very limited amount of the total bandwidth to be used by eMule. The best reaction against this is to change ISP. |
− | + | * Before you are changing your ISP, please verify on the eMule under Options-> Security-> Protocol Obfuscation, that Enable Protocol Obfusaction is checked, otherwise you are unable to work with the Protocol Obfusaction on eMule. | |
− | + | However, by encrypting the eMule protocol, the provider cannot detect eMule easy and might allow more bandwidth to be used by encrypted traffic. | |
− | * | + | * Encryption (obfuscation) is only possible if both sides use encryption. |
− | * | + | * It only protects (limited) against man-in-the-middle attacks. |
− | * | + | * It does not increase your privacy since your data is still visible to other eMule clients that use the same encryption. |
− | + | [image:http://wiki.emule-web.de/image/howtoenableobfuscation.png] | |
− | + | === neomule === | |
− | + | ||
− | + | ||
− | + | ||
− | + | Neomule supported a different kind of obfuscation before official supported obfuscation. THis has become mostly obsolete since official emule supportes it. | |
− | + | ||
− | Neomule supported a different kind of obfuscation before official supported obfuscation. | + | |
== Technical implementation == | == Technical implementation == | ||
− | === | + | ===encrypted UDP=== |
Basic Obfusicated Handshake Protocol UDP: | Basic Obfusicated Handshake Protocol UDP: | ||
Line 56: | Line 51: | ||
a lower CPU usage | a lower CPU usage | ||
− | === Encrypted | + | === Encrypted tcp === |
Basic Obfuscated Handshake Protocol Client <-> Client: | Basic Obfuscated Handshake Protocol Client <-> Client: | ||
Line 112: | Line 107: | ||
- DH Agreement Specifics: sizeof(a) and sizeof(b) = 128 Bits, g = 2, p = dh768_p (see below), sizeof p, s, etc. = 768 bits | - DH Agreement Specifics: sizeof(a) and sizeof(b) = 128 Bits, g = 2, p = dh768_p (see below), sizeof p, s, etc. = 768 bits | ||
− | == | + | == see also == |
− | *[http://www.azureuswiki.com/index.php/Bad_ISPs List of | + | *[[http://www.azureuswiki.com/index.php/Bad_ISPs List of throttling bittorrent isp]] |
− | *[http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=848 Obfuscation | + | *[[http://www.emule-project.net/home/perl/help.cgi?l=1&rm=show_topic&topic_id=848 Obfuscation of emule docs]] |
− | + | ||
− | + | ||
− | + |