Changeset 10818 for dotorg/v6/html/beps
- Timestamp:
- 02/15/2008 02:13:21 AM (11 months ago)
- Files:
-
- 1 modified
-
dotorg/v6/html/beps/bep_0008.html (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
dotorg/v6/html/beps/bep_0008.html
r10817 r10818 38 38 <tr class="field"><th class="field-name">Title:</th><td class="field-body">Tracker Peer Obfuscation</td> 39 39 </tr> 40 <tr class="field"><th class="field-name">Version:</th><td class="field-body">1081 5</td>41 </tr> 42 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="https://svn.bittorrent.com/trac.cgi/browser/dotorg/trunk/html/beps/bep_0008.rst">2008-02-15 0 2:10:08-0800 (Fri, 15 Feb 2008)</a></td>40 <tr class="field"><th class="field-name">Version:</th><td class="field-body">10811</td> 41 </tr> 42 <tr class="field"><th class="field-name">Last-Modified:</th><td class="field-body"><a class="reference external" href="https://svn.bittorrent.com/trac.cgi/browser/dotorg/trunk/html/beps/bep_0008.rst">2008-02-15 00:55:45 -0800 (Fri, 15 Feb 2008)</a></td> 43 43 </tr> 44 44 <tr class="field"><th class="field-name">Author:</th><td class="field-body">David Harrison <dave at bittorrent.com>, Anthony Ciani <tony at ciani.phy.uic.edu>, Arvid Norberg <arvid at bittorrent.com>, Greg Hazel <greg at bittorrent.com></td> … … 134 134 initialization vector then the RC4 key is generated by appending the 135 135 vector to the infohash and then hashing with SHA-1. The resulting 136 hash is then used as the RC4 key.</p> 136 hash is then used as the RC4 key. The string from which the RC4 key 137 is derived whether it be the infohash or the SHA-1 of the 138 initialization vector appended to the infohash is called the 139 <em>intermediate string</em>.</p> 137 140 <p>For example, given infohash <tt class="docutils literal"><span class="pre">aaf4c61ddcc5e8a2dabedef3b482cd9aea9434d</span></tt> 138 141 and initialization vector <tt class="docutils literal"><span class="pre">abcd</span></tt> both represented in hex, the RC4 key … … 300 303 an additional prior exchange of a shared secret. Where trackers now 301 304 maintain mappings from infohash to the corresponding torrent's 302 peerlist and other torrent-specific state, obfuscated trackers would 303 needone additional mapping from <tt class="docutils literal"><span class="pre">sha_ih</span></tt> to the torrent's state.304 Tracker s may also cache the encrypted version of each torrent's305 t racker peer list, to increase computational performance at the306 expense of increasingmemory footprint by a constant factor.</p>305 peerlist and other torrent-specific state, obfuscated trackers would need 306 one additional mapping from <tt class="docutils literal"><span class="pre">sha_ih</span></tt> to the torrent's state. 307 Tracker may also store encrypted versions of each torrent's peer list, 308 to increase computation performance at the expense of increasing 309 memory footprint by a constant factor.</p> 307 310 <p>The obfuscation method meets the following criteria:</p> 308 311 <ul class="simple">