
Reverse engineering · Node
Control panel for self-hosted RustDesk
Challenge. The open RustDesk server connects devices and stops there. Accounts, a synced address book and a management panel exist only in the closed paid edition, priced per seat. For anyone self-hosting to avoid depending on someone else's service, buying a closed component puts them back where they started.
Approach & solution. Wrote the missing half: a Node and Express server with SQLite, implementing the same client-API the RustDesk client calls, plus a browser panel with registration, devices and address book. The API contract is undocumented, so it was recovered from the client sources. Three findings paid for the effort: the address book is more reliable served in legacy mode, the api-server address will not fit into the filename config format because a colon is illegal in Windows filenames, and the address book's hash field is a ready-to-use connect credential rather than a fingerprint, so it gets encrypted at rest.
0
per-seat licences
1 host
no external database
open
source published



