Jump to content

µTorrent Stable (3.4.2 build 34944) does not ban peers sending bad data


bottlerockets

Recommended Posts

  • 4 months later...

This is still a problem in build 38913. Links to specific torrents aren't necessary; the reliable method to reproduce it is to make a local peer send bad data. It only happens if you're downloading the piece from multiple peers, so a minimal test environment needs one downloading peer and two uploading peers, at least one of which is sending bad data. There are of course multiple ways to create such a setup, but here's what I did:

  1. Create a trackerless torrent with a large piece size (I used 2MB).
  2. Start two torrent clients and make both of them seeds for this torrent.
  3. Stop the torrent in both clients.
  4. Modify the data that was used to create the torrent without changing its size.
  5. Start the torrent in both clients without re-checking the torrent data.
  6. Start a new instance of µTorrent 3.4.2 build 38913 and add this torrent.
  7. Make sure the downloading client can have multiple connections to the same IP if necessary.
  8. Set a reasonable download rate limit (I used 200kB/s).
  9. Start the torrent in the downloading client and make sure it's downloading blocks of the same piece from both seeding clients.

I took a screenshot of this happening in a completely fresh installation with the default settings:

post-368258-0-21394100-1426374321_thumb.

 

I also tested this scenario with µTorrent 2.2.1, and this bug does not exist in that version.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...