Live data from Hacker News

RustDesk now supports true unattended remote access on Wayland

rustdesk.com

131–140 of 176 posts

Re: RustDesk now supports true unattended remote access on Wayland

#131
post #22

Earlier quoted context omitted.

Tailscale, or any encrypted mesh overlay is perfect for this. Infact I prefer it that way. Rustdesk can do what it does best at its core.

I disagree, modern software should make encrypted connections over something like HTTP3 or QUIC directly so true secure end to end connectivity works. This would make VPN software such as tailscale obsolete.

Secure and censorship-resistant connectivity is very hard. We should compartmentalise and not expect everything to reimplement and maintain their own version of it and focus on specialised solutions that actually work.

What all user-facing software should have is a minimal-overhead connection option to improve performance inside user's tunnel of choice.

Pure QUIC gets blocked easily, SSH requires wrapping, even Tailscale mimicry is basic and they still ignore simple protocol improvements available.

Re: RustDesk now supports true unattended remote access on Wayland

#132
post #58

Earlier quoted context omitted.

Usually the way to be able to even get the login screen is to use DRM/KMS based capture and use uinput for device emulation. It doesn't strictly need root but it does need privileges a user wouldn't have, like access to the DRM card nodes and uinput device. Sunshine does it this way. It entirely sidesteps the problem of X vs Wayland, although this does mean the unattended physical seat can be physically taken over wh…

As I remember, generic DRM interface allows only writing to a framebuffer and not reading from someone's else framebuffer. Do they use some vendor-specific APIs?

Not that I'm aware of. I'm on my phone right now but any KMS driver that supports KMS and dma-bufs should work.

The basic idea is to enumerate the CRTCs to get the relevant framebuffer plane resources and then use dma-buf exports to pass them to an encoder. Reality can be a bit more complex due to the existence of overlay planes but that's the idea.

https://github.com/LizardByte/Sunshine/blob/master/src/platf...

Re: RustDesk now supports true unattended remote access on Wayland

#135
post #115

Earlier quoted context omitted.

their reply in that issue: "We don’t plan to implement this directly, as it is designed for test initially, we do not recommend using RustDesk with a public IP alone, that's also why direct ip access is turned off by default. For security and privacy, we strongly advise using it in combination with a VPN—the VPN tunnel already provides end-to-end encryption, so additional encryption within RustDesk is unnecessary in…

> That said, we welcome community contributions! Many users express interest or share feedback—but very few take the next step and submit a pull request. If you’re able to help, your PR would be greatly appreciated! hate this. "we don't want this on principle... but we would accept it if you did it yourself!" just say you don't feel like it! don't act like it's a bad thing except for when somebody else does it for yo…

> hate this. "we don't want this on principle... but we would accept it if you did it yourself!" just say you don't feel like it! don't act like it's a bad thing except for when somebody else does it for you, that's just dishonest.

What is there to hate here, I don't understand?

They first provide a concise overview of the current situation. Then how they personally feel about it. Finally they leave it open and end it with "If you want it badly enough, we'll accept outside contributions for it".

They're not saying that they're against the feature in principle, they're saying that they themselves don't plan to spend time implementing it, but if users really want it and contribute the feature itself, they'll be happy to maintain it once merged.

This seems like the ideal solution? What would be better here?

Re: RustDesk now supports true unattended remote access on Wayland

#136
post #38

Earlier quoted context omitted.

VNC and RustDesk are both remote desktop solutions, however, Rustdesk is considerably more performant than the VNC family, because the latter primarily sends framebuffer updates, while the former can use modern video codecs and temporal compression to encode screen changes much more efficiently.

> Rustdesk is considerably more performant than the VNC family It consumes, on the client, 800%-1200% CPU AND 8%-10% GPU decode on my NVIDIA card. I opened a bug and they transformed it into a discussion, without any response.

> they transformed it into a discussion, without any response

How dare they.

Re: RustDesk now supports true unattended remote access on Wayland

#137

Earlier quoted context omitted.

That's not really true for quite some time now. Both client and the free server depend on a separate submodule that has no LICENSE file whatsoever. Because of that RustDesk is stuck in a limbo somewhere between open source, source-available and closed source. Also, the whole management of the project seems questionable. Also for some features a dll blob which is not open source is required with no source disclosed at…

That's what BetterDesk is for: https://github.com/UNITRONIX/BetterDesk

Seems like that is just a server implementation that requires you to use stock RustDesk clients. So you can't really have a fully opensource RustDesk-like system without requiring a substantial chunk of unlicensed source code as well as a closed source dll blob(s).

I just glanced over the repo, deployment and comments around it and it seems like unconstrained AI slop or at least the project seems to be led by a person which can't use AI effectively for the purpose of software engineering.

Re: RustDesk now supports true unattended remote access on Wayland

#138
post #56

Earlier quoted context omitted.

> most software in the world uses a basic hash like MD5 or SHA-256 rather than a key derivation function For passwords? Where do you get that information?

Experience? Looking at codebases? The one in question does, in fact, use SHA-256. HN is a bit of a bubble because there's a large demographic of FAANG-tier employees here who work at big tech or unicorn startups, but most software in the world is not made by FAANG or unicorn startups, and the standards are way, way lower than you might think they are if you're used to living in this bubble. For software development p…

>why accept your password being easily compromised 10% of the time?

Those services using md5 aren't doing important things, I hope, so the password for that service hardly matters.

If it does matter, then user long passwords/phrases and rotate every time (or find a better supplier).

Re: RustDesk now supports true unattended remote access on Wayland

#139

Earlier quoted context omitted.

I disagree, modern software should make encrypted connections over something like HTTP3 or QUIC directly so true secure end to end connectivity works. This would make VPN software such as tailscale obsolete.

One of my primary use cases for tailscale/VPN is that I can happily run stuff (grafana, gitea, etc) and not have to be panicked about monitoring for CVEs - I serve it all over HTTPS but I don't want to put it on the public internet if I don't need to.

I just have envoy proxy with the oauth + jwt filter in front of those services. Envoy does the oidc flow with pocket-id so I can use passkeys for authN. Envoy validates the resulting token and does authorization via ACL. Envoy then sends an authorization bearer jwt with the oidc id_token jwt to the backend (for example grafana). Grafana parses and validates the jwt and sets claims as userinfo (username, groups, email).

I think such setups are at least as secure as having tailscale in front of it and they are web standards conform. I dont need a client app like tailscale, I can just use my normal browser and internet conn.

I always make sure envoy/all other apps are on the latest security patcb anyways.

Re: RustDesk now supports true unattended remote access on Wayland

#140
post #18

RustDesk still does not support encrypted connections when self hosting: https://github.com/rustdesk/rustdesk/issues/3714

> 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.

Post reply on HN