6 ms·

> RustDesk still does not support encrypted connections when self hosting Not true at all. RustDesk connections are fully encrypted even when using a self-hos

by wolrah 1mo ago

> RustDesk still does not support encrypted connections when self hosting Not true at all. RustDesk connections are fully encrypted even when using a self-hosted server. What is not supported are encrypted direct endpoint-to-endpoint connections not going through a server at all, because that's not a use case RustDesk is designed for. The feature is intended for testing, which is why it's disabled altogether by default. If your use case is focused on direct connections without a server, RustDesk is the wrong tool for the job. It's an open-source self-hostable analog to Teamviewer, the server is inherent to the design.

anakaine 1mo ago
So, to have end to end encryption you need to do something like: Client -- Relay Server -- Host That's certainly less than ideal since many remote desktop session will not be using a middle-age server but rather be direct between client and host.
- hnarn 1mo ago
  ”Many?” Teamviewer does not work like that which by far is the most popular.
- wolrah 1mo ago
  To establish a connection between client and remote host, you are expected to go through a coordination server which you trust, that can be either the official one or your own self-hosted instance. Your client and the remote host will then attempt to directly connect if possible, only actually sending the display and input streams through a relay server if a direct connection is impossible due to NAT or whatever else. The use case where encryption is not supported is directly connecting by IP address, which is not the intended use for this software. It's an open source analog to TeamViewer, not a replacement for VNC or RDP. The direct connect functionality is there primarily for testing, which is why it's entirely disabled by default and the option to turn it on is buried at the bottom of a dialog that requires elevated privileges to access. If your use case is focused on those direct connections, RustDesk is not aimed at you.

by wolrah 1mo ago

anakaine 1mo ago

So, to have end to end encryption you need to do something like: Client -- Relay Server -- Host That's certainly less than ideal since many remote desktop session will not be using a middle-age server but rather be direct between client and host.

hnarn 1mo ago
”Many?” Teamviewer does not work like that which by far is the most popular.
wolrah 1mo ago
To establish a connection between client and remote host, you are expected to go through a coordination server which you trust, that can be either the official one or your own self-hosted instance. Your client and the remote host will then attempt to directly connect if possible, only actually sending the display and input streams through a relay server if a direct connection is impossible due to NAT or whatever else. The use case where encryption is not supported is directly connecting by IP address, which is not the intended use for this software. It's an open source analog to TeamViewer, not a replacement for VNC or RDP. The direct connect functionality is there primarily for testing, which is why it's entirely disabled by default and the option to turn it on is buried at the bottom of a dialog that requires elevated privileges to access. If your use case is focused on those direct connections, RustDesk is not aimed at you.