rustdesk / rustdesk/rustdesk-server
Allow remote control only from trusted IPs or other ID
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice if the server could manage who has the rights of remote view/control.
Considering some operator's ID and password has leaked somehow (along the public key), anyone on the internet could connect to his computer.
If the remote viewing/control could be restricted, for example, based on IP address, the operator could be in the same network as the server, such as 192.168.0.0/24, that network address could be added on server config and only hosts connecting to the server using an address belonging to it would be allowed to request remote viewing/control. Considering this network isn't routeable on the internet, it acts as an added security layer.
Also, if that option is turned on, not even an ID/password would be viewable on the operator side, so it wouldn't be easily leaked, maybe as a separate config.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the server configuration and authentication or remote-control request handling, then define how trusted IP ranges or IDs would be configured and how permitted and denied connections should be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100