What's New: RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm).
SpoilerComplete changelog::
RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm). RMP 1.4:
- New : Tixati peerId & Key validator.
- New : Upload & Download rate show in Real time.
- New : You can change Upload & Download rate in Real time.
- New : More finished options (seeding, Leeching, Custom (%, Byte, KB, MB, GB)).
- New : Total upload, Total download, Left and Ratio numbers. (Needs translating)
- New : Total upload, Total download and Ratio stop conditions. (Needs translating)
- New : Torrent & over-all settings now save at Tracker update besides at Exit.
- BugFix: uTorrent peerId validator failed in some rare special cases. RMP 1.3.3:
- New : Tixati peerId and key support.
- New : Can't add new torrent while working on another.
- BugFix: Over logging in some cases (Like moving your mouse on tray icon). RMP 1.3.2:
- BugFix: Special log message for empty tracker respond.
- BugFix: Tracker URL is repeated in Trackers ComboBox.
- BugFix: Selected tracker url is not saved correctly.
- BugFix: Can't load HTTPs Tracker URL in some cases.
- BugFix: Can't decode tracker respond if its encoding is gzip. RMP 1.3.1:
- BugFix: Tracker Respond logged as empty text.
- BugFix: TorrentDay trackers URLs not get correctly loading. (Reported: greenberet)
- BugFix: Tracker request not valid for HTTPs trackers. (Working on the latency) RMP 1.3:
- New : GUI icons and arranged controls.
- New : You can now use uTorrent client without memory reader (uT versions >3.4.x, Change bt.randomize_peer_id to false).
- New : You can now use Transmission client without memory reader.
- New : PeerId and Key get generated at start-up by default.
- New : Port generated at start-up IF the port text box is empty.
- New : Tracker URL & Torrent hash is read only now.
- New : All torrent trackers loaded at the start-up and you can choose one to use.
- New : Faster Memory reader and the GUI still responsive while reading memory.(with uT > 3.4.x support)
- New : Memory reader now respect if the PeerID & Key is global or not.
- New : PeerId validation for uTorrent & Transmission peerIds.
- BugFix: PeerId exceptions ignored and always passed as fixed value.
- BugFix: New port generated with 'every' announce.
- BugFix: Wrong Java version detection in special cases (New detection algorithm).
- BugFix: Can't load tracker URL in some cases. (Reported)
- BugFix: RM+ can't remember the last used client between starts.
- Remove: Internal clients removed.
- Remove: Client files update manager is removed.
ClientFile Changelog:
- New : New extension ".pclient" (had to, because of the many changes).
- New : randomize="" attributes for peerId & Key.
- New : urlencoding="upperCase" & urlencoding="lowerCase" to specify %AB or %ab
- New : global="" attributes for peerId & Key.
- New : query {localip},{ipv6},{ip} place-holders support.
- New : headers {customport},{allports} place-holders support.
- New : PeerId type value "uT" or "ut" for generating valid uTorrent peerId without memory reader. <peer_id type="ut"
- New : PeerId type value "Tr" or "tr" for generating valid Transmission peerId without memory reader. <peer_id type="tr"
- New : <peer_id node has exceptions="" attribute now.
- New : <hash node has exceptions="" attribute now.
- Change: No <urlencoding node anymore (use <hash & <peer_id to add exceptions by exceptions="" attribute).
- Change: No value="" in PeerId and key node in client file anymore.
RMP 1.2:
- New : RM+ now simulates the real client accurately.
- Fixed : RM+ doesn't save Torrent's config file if there is no language file loaded.
- Fixed : Couldn't decode tracker respond correctly (Reported: Rebound)
- Fixed : BitComet 0.70 wrong peerID prefix
- UI : SB-I reference in Title bar.
- New : Auto uTorrent peerID prefix -not whole pId- generator.
- Client Files: up-to-date client files serving the new changes.
RMP 1.1:
- Fixed : "Check for updates" button is not greyed while updating.
- Fixed : Wrong add at log window (example : "unNumUpdatesFounjd=Found {0} updates" after update).
- Fixed : No log messages if language file exist.
- New : IPv6 support {ipv6}
- New : New Icon (Thanks anon)
RMP 1.0:
- New : Client updates via SB-I's server.
- Removed: Check for new version at start-up.
- Removed: "Check for new version" CheckBox.
- Removed: "Help with proxies" at "Network" tab.
- Fixed : Wrong Windows(7 X64) version detection.
- Fixed : Wrong Windows(8,8.1) version detection.
- Fixed : Java wrong version detection.
very important points:
- You can now use RatioMaster plus without memory reader if you run it standalone.
- RatioMaster's Client files is not valid for the plus version anymore.
I came across this post while reading another one and I opened that qBittorrent 3.3.6.rar
I created my own QBT client file for the Vuze "VEM" client and in my file the parameter client name has value "qBittorrent v3.3.6" with the "v" before 3.3.6
But I know that this param is sent across peers. To illustrate this, check the following screenshot (click on the tiny image to see it bigger) I made from a PC that is leeching a torrent:
line 1 is a peer using your spoof client name in which I added the extra "hello spoof" text to show that there is more than just the announce
line 2 is a peer using your spoof client name "as is"
line 3 is a peer using the legit Qbitorrent client
The announce is however identical between line 1 and 2.
I think that missing the "v" could reveal your spoofing. If I can see it (without effort and being a noob), then I believe a tracker could also see it and realize the client is a fake.
But since I'm no expert at all, I could just be paranoid.
I think that missing the "v" could reveal your spoofing. If I can see it (without effort and being a noob), then I believe a tracker could also see it and realize the client is a fake.
But since I'm no expert at all, I could just be paranoid.
Trackers don't read that version string (although they could do it, by emulating a peer and connecting to you), but any difference between the real client and what Vuze sends makes the spoof not perfect, and should be corrected.
"I just remembered something that happened a long time ago."
Trackers don't read that version string (although they could do it, by emulating a peer and connecting to you), but any difference between the real client and what Vuze sends makes the spoof not perfect, and should be corrected.
my thoughts exactly!
we ought to aim for perfection
My system tray running 20 instances of rm+, it almost makes me want to go back to using rm... I mean this one (RatioMaster.NET 0.43)
Also would something like charlesproxy.com/ (available cracked at your favourite general tracker) be better for sniffing tracker announces? Works with https also.
Waiting for new version to :(
My system tray running 20 instances of rm+, it almost makes me want to go back to using rm... I mean this one (RatioMaster.NET 0.43)
You only have two options ? using Rm+ or a very detectable fork of Rm ?
Don't ever use a ratio tool from outside of SB-I. A tracker can detect this version from the very first announce.
I remember that there was a tracker was responding by a message "Stop using ratio master" or something like that.
If you want to use a safe ratio tool you can always use mRatio, it's very valid and well written ratio tool. or wait a couple of days, we have to double check everything. mmmmm is working so hard on beta testing the new version (Thanks man) and we're filling every bug he found.
Also would something like charlesproxy.com/ (available cracked at your favourite general tracker) be better for sniffing tracker announces? Works with https also.
Bookmarks