rustdesk / rustdesk/rustdesk-server-pro

[Feature Request] Restrict Admin Access and Control Initiation to Internal Network

Open
#1,012 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
317
Forks
119
PR merge metrics
No merged PRs in 30d

Description

Description:

I would like to request a security enhancement for RustDesk Server Pro to enforce strict network-based access controls. In enterprise environments, it is crucial to separate the permissions of the internal corporate network (where admins and support staff operate) from the public internet (where remote endpoints are located).

Specifically, we need the following two access restrictions:

1. Internal-Only Admin Access

There should be a configuration option (e.g., via IP whitelisting or interface binding) to restrict access to the Admin Panel. Logging into the RustDesk Server as an administrator should only be possible from specific internal subnets/IPs. Any login attempts from the public internet should be blocked.

2. Restrict Public Relay to "Target-Only" Mode (Block Control Initiation)

For the Relay server exposed to the public internet, we need a setting that allows external clients to register and receive connections (act as targets/hosts), but strictly blocks them from initiating remote control sessions against other users. The ability to control another machine (acting as a viewer/controller) should be strictly limited to users connecting from the internal network.

Use Case / Security Benefit:

This significantly reduces the attack surface. By implementing these restrictions, even if a bad actor compromises user credentials, they cannot access the admin console or use the public-facing relay to pivot and hijack other machines from outside the corporate network.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by mapping the Admin Panel authentication path and public Relay connection roles, then identify existing configuration and network-boundary tests; done means internal-only admin login and target-only public relay behavior are configurable and covered by tests.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, authorization, networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.