mRatio Fixer v7

[anon]

SB-Innovation Presents

>>>>>> mRatio Fixer v7 <<<<<<





╔═══════════════════════════╗
Coded by:
╚═══════════════════════════╝

>>>>>> anon <<<<<<
>>>>>> mitmproxy Project <<<<<<
>>>>>> Iain Patterson <<<<<<
>>>>>> Alireza Dabiri Nejad <<<<<<
>>>>>> Mark Russinovich <<<<<<
>>>>>> Ron Yorston <<<<<<

╔═══════════════════════════╗
Credits:
╚═══════════════════════════╝

>>>>>> ar_avishek <<<<<<
>>>>>> AxiomaticDirection <<<<<<
>>>>>> banjje <<<<<<
>>>>>> H265 <<<<<<
>>>>>> JohnareyouOK <<<<<<
>>>>>> sashiagustina <<<<<<
>>>>>> sigduwksnsksis9283 <<<<<<
>>>>>> snowfox373 <<<<<<
>>>>>> weixin <<<<<<

╔═══════════════════════════╗
Features:
╚═══════════════════════════╝

· Fixes the "received an unexpected EOF or 0 bytes from the transport stream" error (caused by lack of TLS 1.2 support)
· Fixes the "object reference not set to an instance of an object" error (caused by response compression)
· Fixes the "a call to SSPI failed" error (exact cause unknown)
· Fixes the "input string was not in a correct format" and "bencode data is incorrect" errors (caused by chunked responses)
· Can run interactively or as a service
· Includes mRatio multiple instance unlocker and patcher

╔═══════════════════════════╗
How to use:
╚═══════════════════════════╝

1. Download the attachment and extract it somewhere
2. Run start.bat as administrator; wait until it's fully initialized and leave it open
3. Run install_cert.bat as administrator
4. Open mRatio and configure this proxy in the preferences: type SOCKS5, host 127.0.0.1, port 8080
5. Use mRatio normally

Note that the "mRatio Fixer" terminal window must remain open at all times. You can use install_service.bat to install it as a system service instead. This will make it run invisibly and automatically on Windows startup.

╔═══════════════════════════╗
Changelog:
╚═══════════════════════════╝

mRatio Fixer v7
· The correct destination port is now autodetected for all trackers
· Switched from mitmweb to mitmdump to greatly reduce memory usage
· Fixed the "input string was not in a correct format" and "bencode data is incorrect" errors
· Tracker responses are now always fully decoded and normalized before they are passed to mRatio. This slightly increases CPU usage but should future-proof against other errors (e.g. "unknown HTTP response")
· Upgraded TLS cipher list to Windows 10 emulation mode
· Added administrator privilege check to all scripts
· The uninstaller now deletes leftover files from old versions, all the way back to TLS Fix v1 [BETA]
· Left beta stage as development has been active for over a year now

Spoiler Previous versions:

mRatio Fixer v6 [BETA]
· Downgraded mitmproxy and its configuration file to version 4.0.4 (should fix the memory leaks and "specified module could not be found"/"failed to execute script mitmweb" errors)
· Renamed redirect.py to fixer.py
· Added mRatio multiple instance unlocker and patcher
· Several code fixes; notably, yes/no prompts can no longer be bypassed by pressing Ctrl+C
· Reviewed Schannel registry entries

mRatio Fixer v5 [BETA]
· Renamed project from "mRatio TLS Fix" to "mRatio Fixer"
· Updated mitmproxy to version 5.1.1
· Renamed scripts (runme is now start, install is now install_cert, service is now install_service)
· Fixed the "object reference not set to an instance of an object" error
· Fixed the "a call to SSPI failed" error
· Added uninstall.bat script to do a complete uninstall and remove all traces
· Added stop.bat script for those who can't press Ctrl+Break

mRatio TLS Fix v4 [BETA]
· Updated mitmproxy to v5.0.1
· Added the ability to run as a Windows service

mRatio TLS Fix v3 [BETA]
· Preliminary fix for the "specified module could not be found"/"failed to execute script mitmweb" error

mRatio TLS Fix v2 [BETA]
· Updated mitmproxy and its configuration file to v5.0.0
· Added a repair function to runme.bat: you can now delete the file "firstrun" to uninstall and delete the root certificate, then generate and install a new one

mRatio TLS Fix v1 [BETA]
· Initial release

╔═══════════════════════════╗
Known issues:
╚═══════════════════════════╝

· Changes to mRatio's proxy settings do not apply retroactively, so existing torrents will not be affected.
Workaround: remove and readd torrents, or use the procedure detailed at https://www.sb-innovation.de/showthread.php?p=359303.

· If installed as a service, startup may fail with error code 1053. The cause of this is unknown.
Workaround: extract to a different path outside your profile directory and without spaces, e.g. "C:\mRatioFixer".

· stop.bat may fail if msvcp140.dll cannot be found.
Solution: install the x86 Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 from https://support.microsoft.com/en-us/help/2977003/.

· Only Windows 7 x86 and above are supported.
Workarounds involving running inside a virtual machine or separate computer, then modifying the configuration file and proxy settings accordingly may be possible, but I am not able to assist with or debug such setups.

╔═══════════════════════════╗
Technical information:
╚═══════════════════════════╝

· This is basically a neatly packaged and scripted version of mitmproxy, plus some executables that perform certain other tasks.
· All of them are unmodified from the originals, only renamed to avoid accidental execution.

· mitmdump.---: version 4.0.4 of mitmdump
· nssm.---: version 2.24.0.74 (32-bit) of nssm
· windows-kill.---: version 1.1.4 (32-bit) of windows-kill
· handle.---: version 4.22.0.0 (32-bit) of Sysinternals Handle
· busybox.---: version 1.33.0-FRP-3578-g359211429 (32-bit) of busybox-w32

· start.bat: starts Fixer, ensures a consistent status beforehand
· install_cert.bat: installs mitmproxy's certificate
· install_service.bat: installs Fixer as a service
· stop.bat: stops Fixer cleanly if you can't press Ctrl+Break (only for interactive mode!)
· uninstall.bat: stops Fixer cleanly and removes all traces of it
· inst_patch.bat: patches mRatio's executable to allow running multiple instances
· inst_unlock.bat: closes mRatio's BaseNamedObjects handles to allow running multiple instances

· config.yaml: configuration file for mitmdump
· fixer.py: Python script used by mitmdump to process requests and responses
· registry.---: registry file, sets Schannel settings to certain values that fix the "a call to SSPI failed" error
· registry_u.---: registry file, resets the Schannel changes to Windows defaults

[mmmmm]

>>>>>> mRatio Fixer v7 <<<<<<


╔═══════════════════════════╗
Features:
╚═══════════════════════════╝

· Fixes the "received an unexpected EOF or 0 bytes from the transport stream" error (caused by lack of TLS 1.2 support)
· Fixes the "object reference not set to an instance of an object" error (caused by response compression)
· Fixes the "a call to SSPI failed" error (exact cause unknown)
· Fixes the "input string was not in a correct format" and "bencode data is incorrect" errors (caused by chunked responses)
· Can run interactively or as a service
· Includes mRatio multiple instance unlocker and patcher

also fixing

Invalid compressed gzip data

[mmmmm]

It's the logs from Fixer that I need. Those are in the terminal window if you used start.bat, or a .log file if you installed this as a service.

found this error at terminal , maybe useful for next fixer update .

127.0.0.1:60177: clientconnect
127.0.0.1:60177: Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)


mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:60177: clientdisconnect
127.0.0.1:60186: clientconnect

something else

127.0.0.1:55332: clientdisconnect
127.0.0.1:55334: clientconnect
127.0.0.1:55334: Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
  File "mitmproxy\connections.py", line 139, in convert_to_tls
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
  File "mitmproxy\connections.py", line 139, in convert_to_tls
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)


mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:55334: clientdisconnect

anon
can you update it to the last versions ?
since this one from

10.12.20

but the last mitmproxy is Nov 2, 2022 , off-course when you got some free time .

[anon]

mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)


mitmproxy has crashed!

Well, that's bad If you can isolate one or more .torrent files that trigger these errors consistently, I'd be very interested to see them!

the last mitmproxy is Nov 2, 2022

The mitmproxy in v7 already wasn't current at the time of release, but I had to do that to maintain Windows 7 compatibility and avoid a memory leak in the then-latest version.

With that said, there's a possibility of updating the project to v8... stay tuned!

[mmmmm]

Well, that's bad If you can isolate one or more .torrent files that trigger these errors consistently, I'd be very interested to see them!

The mitmproxy in v7 already wasn't current at the time of release, but I had to do that to maintain Windows 7 compatibility and avoid a memory leak in the then-latest version.

i don't know which one cause the crash but am watching ,
i can send you list of those trackers using fixer7 .

With that said, there's a possibility of updating the project to v8... stay tuned!

anon

can you add something at the .bat to show the time ?

i searched and found this but don't know which one and where ?

by the way the crash happen again .

[mmmmm]

i think found one of four crashes :
The handshake failed due to an unexpected packet format.
Retrying in 30s.

sent you another torrent from the same tracker (untouched) at PM .

[anon]

can you add something at the .bat to show the time ?

Error messages come from the mitmproxy process, but if you replace the contents of fixer.py with this, you can add a basic yet effective logging feature.

https://paste.ggc-project.de/?018459a5dfbe3231#EM14EAKCYquSCvcUU7rbXX3gAuiPP5G8a2nMaJnndBpR

No need to restart Fixer as the change applies immediately.

i think found one of four crashes :
The handshake failed due to an unexpected packet format.
Retrying in 30s.

sent you another torrent from the same tracker (untouched) at PM .

Thanks, this one has happened before but it is very hard to reproduce, so I never found what causes it or if it's something I can fix at all.

I found a way to upgrade mitmproxy without dropping Windows 7 support, so I'm hoping switching to the latest version will finally end weird bugs like these (there were major changes in the engine since 4.0.4).

[mmmmm]

Error messages come from the mitmproxy process, but if you replace the contents of fixer.py with this, you can add a basic yet effective logging feature.

https://paste.ggc-project.de/?018459a5dfbe3231#EM14EAKCYquSCvcUU7rbXX3gAuiPP5G8a2nMaJnndBpR

No need to restart Fixer as the change applies immediately.

now its show the time and the tracker , perfect ,thanks

Thanks, this one has happened before but it is very hard to reproduce, so I never found what causes it or if it's something I can fix at all.

I found a way to upgrade mitmproxy without dropping Windows 7 support, so I'm hoping switching to the latest version will finally end weird bugs like these (there were major changes in the engine since 4.0.4).

[mmmmm]

Error messages come from the mitmproxy process, but if you replace the contents of fixer.py with this, you can add a basic yet effective logging feature.

https://paste.ggc-project.de/?018459a5dfbe3231#EM14EAKCYquSCvcUU7rbXX3gAuiPP5G8a2nMaJnndBpR

No need to restart Fixer as the change applies immediately.

its more easy now with the time and tracker

sent you a torrent from the second tracker cause crash
can you check the certificate of this tracker maybe there is a problem with it .

[mmmmm]

i found the others two trackers if you still interested .

another errors :

127.0.0.1:61158: Client Handshake failed. The client may not trust the proxy's certificate for bwtorrents.tv.

127.0.0.1:60544: SOCKS5 mode failure: TcpDisconnect('[WinError 10054] An existing connection was forcibly closed by the remote host',)

[anon]

Okay, I checked everything you sent me.

• Connection was forcibly closed: haven't managed to replicate this so far. The message merely means the TCP connection was reset on the server side and there are many possible reasons for that.
• mitmproxy has crashed: your logs indicate it is caused by the above error, which normally shouldn't be fatal...
• Unexpected packet format: haven't managed to replicate this one either. This error means the tracker is not returning a valid response to the initial TLS Client Hello packet. The best I can do is capturing traffic in hopes of eventually encountering it, then check what exactly is being sent (and I'm doing that right now).
• Client handshake failed: as per https://www.sb-innovation.de/showthread.php?p=360275 this may be caused by or be interconnected to the others.

None of the trackers you sent me have any bad certificates or TLS misconfigurations. The best I can do while I continue running tests is giving you a second update to fixer.py; this one strips some more long HTTP headers, and if the crashes still occur, the extra logging will tell us whether it's before or after processing the response.

https://paste.ggc-project.de/?d5d87f686c008867#6GBedd5JzVsUfi6coob9YTutxohQJCrsTg3y6omYf7WD

[mmmmm]

[2023-05-01 15:34:51.927766] Making https connection to bwtorrents.tv:443
127.0.0.1:53897: clientconnect
127.0.0.1:53897: Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
  File "mitmproxy\connections.py", line 139, in convert_to_tls
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 281, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 386, in _establish_tls_with_client
  File "mitmproxy\connections.py", line 139, in convert_to_tls
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)


mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy
127.0.0.1:53897: clientdisconnect
127.0.0.1:53898: clientconnect
[2023-05-01 15:34:54.873724] Making https connection to bwtorrents.tv:443

127.0.0.1:57160: clientconnect
[2023-05-01 18:24:24.433874] Making https connection to digitalcore.club:443
[2023-05-01 18:24:25.253397] Processing response from digitalcore.club:443 as https
127.0.0.1:57160: clientdisconnect
127.0.0.1:57220: clientconnect
Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)

127.0.0.1:57220: Traceback (most recent call last):
  File "mitmproxy\net\tcp.py", line 197, in peek
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "mitmproxy\proxy\server.py", line 121, in handle
  File "mitmproxy\proxy\modes\socks_proxy.py", line 54, in __call__
  File "mitmproxy\proxy\protocol\tls.py", line 245, in __call__
  File "mitmproxy\net\tls.py", line 468, in from_file
  File "mitmproxy\net\tls.py", line 401, in get_client_hello
  File "mitmproxy\net\tcp.py", line 199, in peek
mitmproxy.exceptions.TcpException: ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)
mitmproxy has crashed!
Please lodge a bug report at: https://github.com/mitmproxy/mitmproxy

127.0.0.1:57220: clientdisconnect
127.0.0.1:57221: clientconnect
[2023-05-01 18:27:48.711760] Making https connection to torrentland.li:443
[2023-05-01 18:27:49.492994] Processing response from torrentland.li:443 as https
[2023-05-01 18:27:49.492994] Killing HTTP header "X-RateLimit-Limit" in response
[2023-05-01 18:27:49.492994] Killing HTTP header "X-RateLimit-Remaining" in response
[2023-05-01 18:27:49.492994] Killing HTTP header "Permissions-Policy" in response
127.0.0.1:57221: clientdisconnect

[anon]

Those logs show the connection is reset before receiving a response. So it's either something at the network level, or the tracker doesn't like the request and immediately sends a RST (but that's unlikely since all we do is parse the Host header and change the TCP destination port if required)

Since I haven't managed to encounter any of these so far, I don't have any other ideas for now I think I'll focus on upgrading to mitmproxy 9, and if the problems continue, make a special debug build to get more data.

[mmmmm]

Those logs show the connection is reset before receiving a response. So it's either something at the network level, or the tracker doesn't like the request and immediately sends a RST (but that's unlikely since all we do is parse the Host header and change the TCP destination port if required)

Since I haven't managed to encounter any of these so far, I don't have any other ideas for now I think I'll focus on upgrading to mitmproxy 9, and if the problems continue, make a special debug build to get more data.

so no more logs until you upgrade mitmproxy 9 , that's the good news
waiting your free time

[anon]

Not dead.

[nageshnarian]

using mRatio without fixer. Can i start using fixer and continue with the existing seeding list in mRatio?

Update: Got it from tutorial.