View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005926 | CentOS-6 | -OTHER | public | 2012-08-31 20:32 | 2013-01-17 23:10 |
Reporter | avij | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 6.3 | ||||
Target Version | 6.4 | ||||
Summary | 0005926: Private bit set in CentOS 6.3 torrents | ||||
Description | In addition to the traditional setup where Bittorrent clients ask the tracker for peer information, Bittorrent clients can also discover other peers by themselves by using some sort of a distributed hash table (DHT). DHT is not used if the torrent is marked as private. It appears that CentOS 6.3 torrents were made with the private bit set. I'm currently seeding 357 OSS torrents, of which only 9 are marked as private (6 CentOS 6.3 torrents, OpenDisc.10.12, salix(64)?-mate-13.37), so the trend is clearly to have the torrent's private bit cleared in open source torrents. Torrents prior to 6.3 didn't have the private bit set. | ||||
Steps To Reproduce | $ transmission-show CentOS-6.3-x86_64-bin-DVD1to2.torrent Observe the Privacy field. Older versions of transmission don't have transmission-show, but instead transmission-cli -i can be used to examine the status of the private bit. http://torrenteditor.com/ can also be used to examine the private bit status. | ||||
Additional Information | The -p flag of mktorrent controls the private bit. Changing the private bit now would change the info hashes, thus splitting the torrent swarm. This may be undesirable. Please make sure the private bit is unset in upcoming releases (5.9 and 6.4). | ||||
Tags | QA-5.9, QA-6.4 | ||||