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.

Latest bitcomet launches itself