Changeset 11138

Show
Ignore:
Timestamp:
09/04/2008 04:03:39 PM (4 months ago)
Author:
dave
Message:

updated to include text requiring peer to drop connections when switching between swarms.

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • dotorg/trunk/html/beps/bep_0027.rst

    r11128 r11138  
    1515IETF RFC 2119 [#RFC-2119]_. 
    1616 
    17 A *private tracker* restricts access to the torrents it tracks.  A  
    18 torrent with restricted access is called a *private torrent*.  To 
    19 promote sharing, private trackers often maintain statistics about 
    20 registered users and restrict access to certain or all torrents for 
    21 users that do not adequately upload. 
     17A *private tracker* restricts access to the torrents it tracks.  A 
     18torrent with restricted access is called a *private torrent*.  All 
     19other torrents are *public torrents*.  To promote sharing, private 
     20trackers often maintain statistics about registered users and restrict 
     21access to certain or all torrents for users that do not adequately 
     22upload. 
    2223 
    2324When generating a metainfo file, users denote a torrent as private by 
     
    2930private tracker, and MUST ONLY initiate connections to peers returned 
    3031from the private tracker. 
     32 
     33When multiple trackers appear in the *announce-list* in the metainfo 
     34file of a private torrent (see multitracker extension in [#BEP-12]_), 
     35each peer MUST use only one tracker at a time and only switch between 
     36trackers when the current tracker fails.  When switching between 
     37trackers, the peer MUST disconnect from all current peers and 
     38reconnect only to those provided from the new tracker. 
    3139 
    3240Rationale 
     
    5967with the intruder would provide the intruder with a full complement of 
    6068peers. 
     69 
     70When a peer switches between trackers, the peer drops connections so 
     71that it cannot become an ongoing bridge between peers granted access 
     72from a private tracker and peers announcing to a public tracker.  This 
     73partially mitigates the effect of an attacker modifying a metainfo 
     74file's *announce-list* and redistributing the file, e.g., via a public 
     75tracker web site. 
    6176 
    6277