Skip to content

ConsoleRDP 1.0.3

Choose a tag to compare

View all tags
@billsecond billsecond released this 04 May 17:13
· 2 commits to main since this release
v1.0.3
d3eb346

ConsoleRDP 1.0.3 — fully automated RDP setup

The biggest pain point in 1.0.0–1.0.2: after install you still had to open Plasma's System Settings → Remote Desktop, toggle it on, set a username/password, and apply. mstsc would not connect until you did that. 1.0.3 removes that step entirely.

What changed

consolerdp-configure now has a step 7/8 that:

  • Generates a self-signed RSA-2048 TLS cert (10-year validity) at
    ~/.local/share/krdpserver/krdp.{crt,key} — required for NLA, no
    warning prompt at first connect.
  • Writes ~/.config/krdpserverrc with SystemUserEnabled=true and
    Autostart=true. With the NLA patch in our krdp build, this means
    mstsc authenticates against PAM — the seat user's Linux password
    is the RDP password. No KCM-managed user, no KWallet entry.
  • Runs loginctl enable-linger so the user manager survives reboots.
  • Runs systemctl --user enable --now app-org.kde.krdpserver.service.

install.sh adds openssl to its apt package list (always present on
Kubuntu but pinned explicitly for minimal ubuntu + kubuntu-desktop
installs).

After install

Open mstsc on Windows:

Field Value
Computer <linux-host-ip>:3389
Username your Linux username (the --user you passed)
Password your Linux password (same one as SDDM/sudo)

That's it. mstsc will warn about the self-signed cert on first connect; tick "Don't ask again for this computer" and it never warns again.

Upgrade from 1.0.x

Re-run the bootstrap on top of the existing install:

curl -fsSL https://github.com/billsecond/consolerdp/releases/latest/download/install-remote.sh -o /tmp/install-remote.sh
sudo bash /tmp/install-remote.sh

It's idempotent — won't overwrite an existing TLS cert, won't change consolerdp.conf if you've edited it.

Assets 4
Loading