Sure. It risks introducing vulnerabilities. It needs to be implemented very carefully. I think a built in version, with security in mind, is a lower risk than relying on users to implement their own solution, and risk them picking the wrong one or setting it up incorrectly.

Every user convenience introduces vulnerabilities. The users are the weakest link in every system. It’s a balancing act, and one I don’t think Linux has ever balanced well for usability. But server core has shown there’s no reason for the service to be on by default. There’s much more dangerous Linux features that are switched on by default configs, like root logins and password authentication, so let’s not pretend Linux has ever taken a hard line on this.

I actually just tried moonlight/sunshine this past week for gaming, and I was disappointed. The interface is missing critical components that Steam link has. Makes it almost useless unless you have a keyboard attached in many cases.

But I hadn’t thought of using it for Remote Desktop into Linux. Sounds a lot better than No Machine. Thanks for the tip.

I remember in college we had access to a Unix box via these computers that remoted into it. I don’t know the technical details, but I was able to log in with my account and it was presented as a GUI on my end. We used No Machine as the client if that’s relevant. I wonder how something like that can be set up.

Those names. Moonlight is a gui for ghostscript for easy pdf-compression, too.

K. And what massive vulnerabilities have been introduced by that? I’ve seen no articles or sources backing that claim.