Printable View
As of version 4.0.4, this client uses an individual peer_id, so it's okay to run both RatioMaster Plus and qBittorrent at the same time. As of version 4.3.0, anonymous mode has no effect on announce requests for private torrents, so enabling it shouldn't be a detection vector.
This client emulates the following settings, so make sure your real qBittorrent 4.4.4 also uses them:
- Encryption mode: Allow encryption
- Optional IP address to bind to: All addresses
That's quick. Thanks for sharing
Seconded. Hope you or others can take on mRatio and Extreme Mod at some point. Once you're familiar with mCreator and .client file syntax, it's basically applying the same changes as in rmcMaker on both, and you can have three for the price of one!
I'm not a very good technician.Quote:
Originally Posted by anon
I remind that I stupidly just copy « anon »'s work by changing all references I find (4.4.x.y) without touching anything else...
So I'm a little scared. I'm trying « mCreator »
Before making an official post I would need someone qualified to check what I have just updated.
I touched :
? Emulation name (qBittorrent 4.4.2 ? qBittorrent 4.4.4)
? Author (required)
? PeerID (-qB4420-[0-9a-zA-Z\-\._~!*()]{12} ? -qB4440-[0-9a-zA-Z\-\._~!*() ]{12})
? Announce Get (User-Agent: qBittorrent/4.4.2 ? User-Agent: qBittorrent/4.4.4)
If everything is correct I could continue on my own for future update.
Here the attempt : Attachment 21373 for mCreator
Unfortunately I can't check your work right now, but if anything, mCreator is easier. Process name and reserved bytes are not required, and everything else is identical to rmcMaker. If you've made the same changes in the same way, the emulation is accurate.
For Extreme Mod, you have to check the reserved bytes and LTEP client identification string by capturing an unencrypted peer handshake with Wireshark. Also, the syntax for everything is different, but that's what we have documentation for.
Client file has been verified correctly!