Am I missing something here? Why is this designed so that you can’t remote into a KDE desktop until you’re logged in locally (my place of employment would never allow an automatic login to occur). With Gnome it works as expected (well sort of, you still have to log in twice - but at least it lets you remote in without being already logged in at the machine), so I was surprised that I was unable to use KDE in a remote desktop scenario without already being logged in at the machine - unless there’s something I’m misunderstanding here?
The other issue is that people can see your screen and what you are doing when you remote in - which is considered a security risk at my place of employment. I haven’t tested to see if Gnome does that as well.
You’re not missing anything.
RDP is for sharing an already running user session; you’re comparing it to a different type of solution.
It must be tied to a logged-in user session.
SDDM didn’t support remote login for security reasons.
GNOME introduced a headless RDP feature… creating a new, isolated session.
I think fully headless, non-shadow sessions might be on the KDE Development radar, but not currently in the mix.
What do you mean by this? When I use RDP/RDC on Windows it locks the screen locally, and works before a local log in - is that not the way it was designed to work? Or do you just mean that’s what the solution’s concept is on KDE?
Right, again - Windows RDP creates a new isolated virtual session.
KDE Plasma’s KRdp is ‘Session Shadowing’… it is a user-level, not a system-level service.
The new Plasma Login Manager is being developed to specifically work on such issues, to start headless Wayland sessions for RDP to bring KDE up to par.
Got ya, so in the KDE context then. Thanks! Looking forward to seeing the solution for this implemented so that I can use KDE on my office PC.
i am mostly ignorant on all things networking, so forgive me if this sounds insane.
why couldn’t you ssh into the remove machine and start a plasma shell there remotely to RDP into?
you would essentially be logging in twice, just like on gnome.
Hmm… I’ll try that out. Definitely not a great long-term solution for a general user, but could be a good workaround for myself until a more complete remote login solution is implemented. I appreciate it.
Interesting question.
I was a Network Administrator for 43 years, Lockheed, Raytheon and Qualcomm. At Lockheed I was cleared for ‘Deep Black’ Programs that I’ve got to take to my grave with me. When I say ‘cleared’ I mean FBI, DEA, D.O.D., NSA, CIA, DARPA (Defense Advanced Research Projects Agency). It took six months from start to finish.
Your company apparently has concerns about security issues. If you are working with Programs such as I was, your employment will terminate fast, so it’s hardly worth the risk and you’ll never again work with any Corporation that has any ties to the D.O.D. You’ll be Blacklisted.
If the company you work for has it’s own policies for considering it a security risk - and I cannot think of any other than risks of Malware, et al., you’re still likely to be canned. Maybe they are concerned about Ransomware, who knows.
Is it worth the risk?
Nothing that serious, it’s a higher-ed institution. They allow staff/faculty to remote into their Windows desktops, I’m just trying to replicate the experience on a Fedora KDE desktop.
They are tightening security though, it has been a focus for the last couple of years after a malware/ransomware incident.