This is a discussion on [BUG] DHT connecting on private torrents with BitComet v0.60 within the Bugs and Feature Requests forums, part of the BitComet Technical Support category; When I was seed a torrent on a private tracker I saw that there were people connected too the torrent ...
When I was seed a torrent on a private tracker I saw that there were people connected too the torrent that was not connecting from the site. When I clicked on the Tab "trackers" I saw that there were the sites tracker and DHT network. Why is this one activated when it shouldn't be?
DHT is enabled by default for public torrents. It sounds like the torrent creator hasn't made a SecureTorrent, so DHT and peer exchange can still be used -- if the private flag is enabled, DHT and peer exchange are disabled in the client and cannot be re-enabled (the check boxes are un-checked and greyed out).
The problem isn't with BitComet, it's with the torrent creator making a public torrent and sharing it on a private tracker.
2 problems.
1. some idiot uploaded the private torrent onto a site like mininova/torrentspy and got people to connect via dht.
2. the site creator did not enforce a "private torrent" rule. some more sophisticated sites that i'm a member of actually configure your uploaded torrent immediately to "private." so if you don't know how to play around with the torrent maker then it's already taken care of.
That's the strange thing! Even if it stands "..DHT network(Banned by tracker)" it still connects too people on the DHT network
Edit: I see now that the two users connected through the DHT-network is also using Bitcomet 0.60. And on the site the two users that are connected through there are using Bittornado and Azereus. And I am connected too all four of them.
It must be something with Bitcomet.
I'm using Bitcomet 0.60, I'm also having this problem...
DHT and peer exchange are disabled in the client and cannot be re-enabled (the check boxes are un-checked and greyed out).
But DHT is still returning peers and i'm still connecting to them !!
Its not a case of people not creating a torrent correctly.
Its a case of Bitcomet not honoring private flags in torrent.
We have been doing some testing. ie we have a user downloading torrent xyz. The user is a leech so is banned on site and his passkey is scrambled.
Bitcomet reports a tracker error then after a certain length of time dht kicks in even though it is disabled in client and the flags are added by the site when the torrent is downloaded.
We have had no other problems with other clients in the same type of scenario.
It's because people have "Add DHT Network as backup tracker" enabled. This feature exists so if a tracker permanetly goes down BitComet kicks in the DHT so users can continue downloading/uploading. On one hand I hate this feature because it can be abused by leechers, but on the other hand I understand why it exists and agree that it is a useful feature to have.
But to answer your question, no, as far as I know if the user has enabled that option there is no way for the tracker to stop DHT from enabling if the tracker becomes unresponsive. All BitComet is trying to do is help the users finish their transfer if the tracker goes offline, which is the right thing to do when you stop to consider that BitTorrent was not created to use a ratio system.
I understand what you are saying, the bittorrent protocol was not intended for the purpose which it is now used.
However as a private tracker owner we do enforce ratios and because of this we have had to ban bitcomet, which is unfortunate as it is a good client.
If bitcomet did honor the private torrent flag explicitly then we would allow it.
That seems to be the only course of action for now :( Hopefully that problem is remedied in future versions.
It would seem that even if every BT client obeyed a private flag, any user could bypass that rule by editing the text in the torrent to remove the flag. (since doing so would be such a valuable tool for resuming lost neo-trackerless torrents)Originally Posted by DemoN3x
Though admittedly, editing the non-ASCII format in a torrent file is going to require a bit more research compared to a straightforward text edit.
um no, they can't, the private flag is in the info part of the torrent, so if u remove or edit the private field, the info hash changes, thefore making the torrent uselessIt would seem that even if every BT client obeyed a private flag, any user could bypass that rule by editing the text in the torrent to remove the flag. (since doing so would be such a valuable tool for resuming lost neo-trackerless torrents)
Though admittedly, editing the non-ASCII format in a torrent file is going to require a bit more research compared to a straightforward text edit.
To the great woe of our userbase, SceneTorrents is banning BitComet tomorrow due to the # of leaks to DHT. :/
No matter what users who want to find out how to bypass a ban from a "private tracker" will.
So banning the use of BitComet will not solve a thing.
the passkey is what should be banned. Removing the "private" flag will not remove the passkey from what I understand.
If that is a problem then there is also the way that one of the private trackers I use does. They make a small exception plugin that works with most clients and then you just download the exceptions list. It will not allow those people to connect.
Me personally I disable the ability to use a backup tracker or DHT under preferences and when I download a torrent that is not made properly (allows DHT and/or Peer Exchange) I remove those checkmarks as well.
I maintain a good ratio on all the private sites I belong to some of which I have broken 100GB or more in upload alone. I will continue to use BitComet no matter what. If you don't want someone who maitains a good ratio (Ratio: 1.870 on a site that is "banning bitcomet usage") on your site then ban me.
Granted yes maybe BitComet makes it a bit to easy to "bypass" a ban. Eh I don't know and don't care personally. Show me a torrent client that uses the same or LESS resources that allows the same or BETTER control over individual torrents and I may just switch to it. As of yet no one has. I have used Azureus (it sucks high VERY high resource usage), bittornado (not as high resource usage but the control options suck imo), and many others that I have installed and deleted.
The system I use for torrents and torrent related stuff (IRC, RAR, Virusscan, Defrag, etc etc) is only a Celeron 633MHZ with 256MB of ram. With mIRC, BitComet, O&O Defrag, O&O CleverCache, and 3 seperate IE windows open (not CTRL-N'ed but actual seperate windows) my current system load is less than 30%. Yes I run Windows XP Professional.
Yes Private trackers are nice. However torrents are driven by the end user who is SEEDING not the private sites. Private sites only help to protect those who are SEEDING and those who are LEECHING from normally prying eyes in the sense that "big brother" can't download the torrent from you and see who all is using it. But "big brother" can still if they want sniff and gather every single IP accessing the tracker where it is private or not.
To the programmers for BitComet. Keep up the good work. Go ahead and make it so that DHT is always disabled and can not be enabled by the user to lift some of the paranoia but keep on hacking away at it.
Ebolla
Proud user of BitComet
Peace Out
i was set to write a long reply, but...
how about releasing a client with all DHT options unchecked? simple and painless.
why would a company do that The company wants to release a product that will gain popularity fast and to release a client that can get around the "privat Flag" will certainly attract MANY users....
The problem is now to ID the client properly although this may be pointless due to the many countless modification/add-ons that let the client report a different ID to the tracker...
Or a new method of flagging the torrents...
Posting Permissions 
LinkBack URL
About LinkBacks
Bookmarks