rustdesk / rustdesk/rustdesk-server
Encryption always enabled in S6-Overlay image
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.4k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When setting ENCRYPTED_ONLY to 0 in rustdesk-server-s6 image, hbbs in the image still forces encryption and will generate a key. Unencrypted connections are not accepted.
Describe the environment
- Install environment: Docker Compose
- Version: latest(1.1.11-1)
How to Reproduce the bug
Steps to reproduce the behavior:
- Start rustdesk-server-s6:latest image with env variable ENCRYPTED_ONLY set to “0”.
- Find id_ed25519.pub generated in data folder.
- Clients are not allowed to connect without the key.
Expected behavior
Clients are able to connect without the key.
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 by running the rustdesk-server-s6 image with ENCRYPTED_ONLY set to 0 and inspect whether id_ed25519.pub appears in the data folder and whether unencrypted clients can connect. Check how hbbs handles this environment setting in the image. Done means the setting no longer forces key generation or rejects clients without the key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, rust
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100