RustDesk still does not support encrypted connections when self hosting: https://github.com/rustdesk/rustdesk/issues/3714
Your statement is not entirely accurate. This only applies when using Direct IP Access on local networks, which is off by default. Their justification and invitation to PRs is the final comment [1] on the issue you linked. Why are you leaving this information out of your comment? 1 - https://github.com/rustdesk/rustdesk/issues/3714#issuecommen...
RustDesk now supports true unattended remote access on Wayland
171–176 of 176 posts
Re: RustDesk now supports true unattended remote access on Wayland
#172RustDesk should fix their password requirements: https://github.com/rustdesk/rustdesk/discussions/2888
Re: RustDesk now supports true unattended remote access on Wayland
#173Earlier quoted context omitted.
> 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 defau…
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.
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.
Re: RustDesk now supports true unattended remote access on Wayland
#174Earlier quoted context omitted.
Your statement is not entirely accurate. This only applies when using Direct IP Access on local networks, which is off by default. Their justification and invitation to PRs is the final comment [1] on the issue you linked. Why are you leaving this information out of your comment? 1 - https://github.com/rustdesk/rustdesk/issues/3714#issuecommen...
It may only apply to Direct IP Access, but isn't that what many would expect (not trusting middleman to be secure?)
You either pick a middleman you want to trust or you run one of your own, if you don't want that or need the features if offers RustDesk is not for you.
Re: RustDesk now supports true unattended remote access on Wayland
#175Earlier quoted context omitted.
From personal experience, Moonlight is pretty slow and high latency. Even Microsoft's RDP is better.
I don't understand how this can be, you can play competitive games over moonlight/sunshine, and I really don't recall being able to come close to that latency on RDP (though I haven't tried in about a decade)
Re: RustDesk now supports true unattended remote access on Wayland
#176Earlier quoted context omitted.
so without tailscale or any other intermediary turn service how does my computer behind a NAT connect to another computer behind another NAT
by using something like iroh. basically an embedded tailscale.
> The public relays we run have seen more than 200 million endpoints created, in the last 30 days alone