Rustdesk connection is not encrypted although a key is used #1116

Closed
opened 2026-02-20 23:18:38 -05:00 by deekerman · 1 comment
Owner

Originally created by @AlphaDE on GitHub (Dec 6, 2022).

Describe the bug you encountered:

Running my own Rustdesk server with key (-k command) used by the server and all connected clients, the connection window always indicates that the connection is not encrypted (red shield symbol).
The overall connection is fine, access without the key is rejected, key is supplied to hbbr and hbbs with the -k parameter.

What did you expect to happen instead?

Encrypted connection (green symbol).

How did you install RustDesk?

Github docker release

RustDesk version and environment

Rustdesk 1.1.9 on an Ubuntu 20.04.5 LTS under Proxmox.

Originally created by @AlphaDE on GitHub (Dec 6, 2022). <!-- Hey there, thank you for creating an issue! --> **Describe the bug you encountered:** Running my own Rustdesk server with key (-k command) used by the server and all connected clients, the connection window always indicates that the connection is not encrypted (red shield symbol). The overall connection is fine, access without the key is rejected, key is supplied to hbbr and hbbs with the -k parameter. **What did you expect to happen instead?** Encrypted connection (green symbol). **How did you install `RustDesk`?** Github docker release **RustDesk version and environment** Rustdesk 1.1.9 on an Ubuntu 20.04.5 LTS under Proxmox.
deekerman 2026-02-20 23:18:38 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@rustdesk commented on GitHub (Dec 6, 2022):

#763

@rustdesk commented on GitHub (Dec 6, 2022): #763
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/rustdesk-rustdesk#1116
No description provided.