rustdesk / rustdesk/rustdesk-server-pro
Separate key materials for relays
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 317
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
Relating to #1003 , I would like to open a relay to the internet for accessing a local server deployment.
I'm a bit concerned, that relays hold a copy of the main servers private key.
Even if I would only expose port 21117 for relay traffic, it confuses me a bit, that compromising a single relay exposes keys capable of impersonating the central hbbs to all registered clients. Am I missing something big here? The server keypair is not something that can easily be rotated or replaced.
It clearly states that both keys should be copied to every additional hbbr: https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/relay/
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
Start with the relay documentation linked in the issue and the related #1003 discussion. Define the key-separation behavior and its rotation and compromise guarantees, then document or test the accepted design; no repository file or test entry point is named.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100