Search


Rss feeds
Posts Comments Source Code
Rating
Image to SpectrogramNontransitive DicecheaTorrentDomain ColoringiMac G5 CPU Fan view all...
Recent
Pretty GraphHypernova EngineEmergent FeedbackSDL Euclid OrchardSingularity Viewer view all...
Tags

All source code released under the BSD License unless otherwise specified
© 2010, Gavin Black

cheaTorrent

Overview

This is the source tarball of a few simple tweaks to ctorrent. It requires knowledge of how to compile programs and run them from the command line. The people tech savvy enough to use this are likely able to falsify their ratios anyway.

With that said, this bitorrent client has an 'evil' set of defaults. It will not upload to peers, reports back that it has uploaded ~70% of what it has downloaded, immediately closes once downloading is complete, and spoofs it's user agent to a known popular client. This is the default behavior, although some of it can be changed on the command line

There are three reasons I made this:

  • Show that upload stats are worthless for determining level of infringement. They can be set by the users themselves.
  • Show that private trackers are relying on obscurity to ensure people have good ratios. The underlying mechanism used is flawed.
  • Many private trackers have ridiculous ratio requirements. This side steps that issue.

Screenshot

Screenshot of cheaTorrent in action

Source Code

Source Tree: http://devrand.org:8080/cgi-bin/cgit/cheaTorrent/tree/
Snapshots: http://devrand.org:8080/cgi-bin/cgit/cheaTorrent/commit/
Git Access: git clone http://devrand.org:8080/git/cheaTorrent

Conclusion

I didn't change any of the command line options, but would if there was any interest. Also I may, one of these years, add the capability to falsify reported download.



Last Edited: 2010-10-25 02:38:13

+ Add a comment


Gavin Black said (2010-10-25 02:40:10):
That is true that you could detect infeasible ones easily. That's why this falsifies at a steady rate as a fraction of the currently reported download ;)

Stine said (2010-10-25 02:39:19):
Afterthought: I'm by no means an expert on the bt protocol, but isn't it
possible that private trackers could recognize completely infeasible share
ratios? E.g., if the tracker only sees Billy sharing for 1 hr, he /probably/
hasn't hit a ratio of 1.5 on a 1GB file in a typical smallish swarm. Of course
this wouldn't be conclusive, but after repeated offenses I could imagine that
this would lead to catching the banhammer.

I'm interested find out more about anti-ratio spoofing (and anti-anti-ratio
spoofing) techniques out there in the wild.

Stine said (2010-10-25 02:38:51):
Awesome work. Now I can be a total leech on private trackers! :D