rmClient Maker

[Lucius]

Hello,

Here is the new RatioMaster encrypted clients maker. which is support the old school .xml clients so you can easily porting the clients :top:

As always, Thanks mmmmm for the great support.

Known issues

For uTorrent, changes to the build number in the General tab won't be acknowledged by generating a sample peer_id unless the client file is saved and reloaded

[anon]

This program is now public. Opening existing client files should give you a good clue as to its operation and syntax, but feel free to ask any questions here. A nice reference for writing and testing regular expressions is available at http://regexpal.com.s3-website-us-east-1.amazonaws.com/.

Recommended reading: 32021, 33436, 363021

[Lucius]

Don't forget about this very useful tool
https://www.sb-innovation.de/showthread.php?32349-ReportMode-1-0

It makes everything in this post like magic:
https://www.sb-innovation.de/showthread.php?35046-mCreator&p=363021&viewfull=1#post363021

[anon]

You'll need to repost the attachment and help text here though, that thread is in a class-restricted subforum. :happy:

[JohnWick]

Don't forget about this very useful tool
https://www.sb-innovation.de/showthread.php?32349-ReportMode-1-0

It makes everything in this post like magic:
https://www.sb-innovation.de/showthread.php?35046-mCreator&p=363021&viewfull=1#post363021

No permission for report mode

[Lucius]

No permission for report mode

I will open a new thread for it, There is a bug I will fix first then share the updated version with you.

[JohnWick]

This program is now public. Opening existing client files should give you a good clue as to its operation and syntax, but feel free to ask any questions here. A nice reference for writing and testing regular expressions is available at http://regexpal.com.s3-website-us-east-1.amazonaws.com/.

Recommended reading: 32021, 33436, 363021

Good, Is it not good if ratio cheat creation tools and tricks should be public? :klatsch_3:

I am not saying RM or MR source should be public, but there should be tips to create simple cheat tools.

[anon]

Good, Is it not good if ratio cheat creation tools and tricks should be public? :klatsch_3:

There are valid reasons for cheat client authors not to publish source code or documentation in public, because...

...ideally, knowledge of how a system works alone should not be enough to subvert or vulnerate it, but that does not truly apply here because...


...making a 100% perfect cheat client is not possible, and detecting 100% of cheating is not possible, as there are too many idiosyncrasies and fringe cases to consider because...



...ultimately, BitTorrent was not designed for private sharing or centralized tracking of ratios, and while protocol extensions do exist, they cannot implement such a thing in a way that is both secure and backwards compatible.


I am not saying RM or MR source should be public, but there should be tips to create simple cheat tools.

JOAL and ratio-spoof are open source, as are other lesser-known programs. Back in the day, the RatioBlaster and TorrentProxy sources were the go-to reference for aspiring programmers. There is a subforum here dedicated exclusively to documenting how each client handles key aspects of its tracker reporting. Everyone who has asked for help on this regard has received it. Fun fact: I answered every question Owyn had about uTorrent modding when he hadn't yet made mention of doing any, and was one of the betatesters for the first Serenity mods (in plural, the settings manager didn't exist yet).

At the end of the day, though... programming is hard (https://dorinlazar.ro/2021-02-programming-is-hard/), and BitTorrent and HTTP are complex protocols. I'm not saying no one should try - otherwise we wouldn't have all the programs we have here - but here's a suggestion. Write a small cheating program that only starts a torrent, reports a custom amount of upload, then stops it. You will quickly learn how "simple" this really is.

[anon]

Obtaining and validating the reserved bytes takes a bit more work than the rest. 34729 gives a general overview to which I'd like to add some tips.

Under Windows, Wireshark with Npcap is the best method of capturing loopback traffic (and if you're reading this, you likely already have both installed). To get cleaner results, use (tcp port XXXXX || tcp port YYYYY) as a capture filter, where XXXXX and YYYYY are the listen ports configured in the torrent clients you'll be using.
Add a small torrent, preferably one created by yourself exclusively for this purpose that has the private flag set and no trackers defined. One client must be seeding it, and the other must be at 0% done.
Protocol encryption must always be disabled.
To initiate the connection, add 127.0.0.1 as a peer on either client; the port number must be that of the opposite one.

21469 provides an example of an unencrypted handshake between qBittorrent 4.5.1 and Clean uTorrent 3.5.5_46074, followed by the complete download of a 2.25 MB torrent, very much like what you'll get after doing the capture on your own. See if you can find the reserved bytes and LTEP identification string for both peers.

Note mRatio does not connect to peers or respond to incoming connections, and therefore does not require any of this.