mirror of
https://github.com/NohamR/RMHook-Win.git
synced 2026-05-25 12:27:12 +00:00
Compare commits
2 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
b18a63b117 | ||
|
|
634c65afd4 |
@@ -72,6 +72,7 @@ To remove the proxy and restore the original `paho-mqtt3as.dll`:
|
||||
```
|
||||
|
||||
## Configuration
|
||||
When you pair the app the first time, the in-app browser will open `my.remarkable.com` to fetch a one-time pairing code, close the browser and enter the code from `rmfakecloud` direclty into the app prompt.
|
||||
|
||||
Config path:
|
||||
```text
|
||||
@@ -101,6 +102,9 @@ If the config file does not exist, it will be created automatically with default
|
||||
- Check the config file for valid JSON
|
||||
- Make sure the `host` and `port` values point to a reachable rmfakecloud server
|
||||
|
||||
## How it works
|
||||
The project builds a proxy DLL for `paho-mqtt3as.dll` that re-exports all original functions. It hooks specific Qt network functions (`QNetworkAccessManager::createRequest`, `QWebSocket::open` and `MQTTAsync_createWithOptions`) to intercept and modify outgoing requests from the reMarkable Desktop app. The hooks redirect traffic to the configured host and port, allowing the app to communicate with a self-hosted rmfakecloud server instead of the official reMarkable cloud.
|
||||
|
||||
## Credits
|
||||
|
||||
- MinHook: [TsudaKageyu/minhook](https://github.com/TsudaKageyu/minhook) - API hooking framework used by the project
|
||||
|
||||
Reference in New Issue
Block a user