If I'm wrong on something, people need to know who to call on it :-P (similar to sidebar above)Ġ.88 same as above, send stopped event after 4 clicks on stop buttonĠ.89 Sends stopped event properly, still has info_hash/size/filename reportingĠ.90 drops the sending to Ġ.91 drops sending to īTW, I don't mind being named as a source for anything I make public. I don't really want playboy, it's just a good file for testingĠ.86 sends hash to at least 3 places, filename to 2. User-Agent: Mozilla/4.0 (compatible MSIE 6.0 Windows NT 5.1 SV1. And BitComet has actually been doing it for a while now and we didn't even know. This is pretty much exactly what µtorrent has been wrongfully accused of a lot of times in the last year. It is worse case scenario yes but why else would BitComet collect this data secretly (well not really secretly, its so easy to detect its a miracle it didn't hear of this earlier, but sneaky yes cos their privacy police states they don't).
Its the fact that BitComet gets this info from ALL its users and could track most of its users (based on their IP) this way. However this goes for the normal peer-tracker traffic too so from that perspective this isn't an added risk. Any hardware/software/person in the route to the server who is looking at/logging the data could read it no problem. Not only a man-in-the-middle could see it (man-in-the-middle could decrypt information under certain circumstances). The string contains the xml info as shown in the 'Which translates to' part. I fact its a simple html form POST (as opposed to GET) submit with a urlencoded string in the 'query' form field. Updated the post to identify System as my 'reliable source' Harmless? Lying bastards violating their own privacy policy? Attempt at tracking which torrents are downloaded by whom? And of course by connecting to their server they get ur IP connected to that hash.ĭraw your own conclusions. Although they'd still have to find the details that go with that torrent this is not impossible, especially with popular public torrents. Remember that a hash is a unique ID identifying a torrent. Its sending hash, size and this bt thing to its own server. I'd advise everyone to avoid bitcomet use (yet again), because they have proven once more to be the shittiest client out there. The torrent I tested with just happens to be 39MB in size and has an info hash of a0743038e91828fc15db5eec0b2923b1c1518032, which as you can see is sent to BC regardless of what their privacy policy says.
0 kommentar(er)
