In addition, a â€˜privateâ€™ flag within the torrent file tells the BitTorrent client not to share on the DHT network. However, many private tracker operators argue that BitComet does not honor the private flag.

Instead, the torrent is shared on the DHT network and those who do not belong to the private tracker can freely leech off the resources of that community. That is the much simplified story many private trackers are telling. Yet many are not so quick to blame BitComet. BitComet does share private torrents, but only when certain conditions are met. In order for BitComet to share torrents, the following must happen.Īn individual (person 'A') who belongs to a private tracker downloads a torrent. The torrent contains the necessary peer information (such as IP addresses) to initiate the swarm. Person 'A' then uploads the private torrent to a public tracker such as. Person 'A's' IP address, along with private peers, are contained in the torrent file. The private tracker must be completely unreachable.

Person 'A' can achive this by simulating a site outage (for example, by altering the host file.) But for our purposes lets assume the private tracker is suffering a DoS attack and is unreachable for an extended period. The BitComet client will eventually give up trying to reach the private tracker and enables the DHT network.Īt this point, and only at this point, will outsiders be able to access the torrent shared over the DHT network.

Download bitcomet for windows 10