Release RD Panel 0.16.0 · bropines/rdpanel

Share links turn on in the panel, a dropped terminal comes back with its shells, and the Windows installer stops arriving broken.

docker pull ghcr.io/bropines/rdpanel:0.16.0

Share links are a switch in the panel (Settings → Branding → Share page) instead of a redeploy. RDPANEL_SHARE_LINKS_ENABLED is only the starting value now, and the section is there even while the feature is off — it used to be hidden behind the very flag that turned it on.
The web client's terminal can open as administrator on a Windows device: it asks for a Windows administrator account, which the device verifies itself and refuses unless it really is one, and the shells then run under the device's own account. The password is held in the page and stored nowhere, so reattaching asks again.
A monitor picker on the toolbar: the device's monitors with their names and resolutions, instead of stepping through them one at a time.
Inline images in the terminal — SIXEL and iTerm's protocol, so timg, chafa and the plotting tools draw for real. Not from a Windows device: the pseudoconsole there rebuilds the output from a text buffer and an image has no place in it.
The session settings and the default connection settings are centred modals with display and control side by side, instead of a side sheet and one long column.
A terminal left open stays open: it probes an idle connection, which a relay drops after 30 seconds of silence.

A dropped terminal no longer loses its shells. Every real drop — a sleeping laptop, a relay timing out — looked like the device hanging up, so the panel forgot the shells' service id while the device kept them running, with nothing in the protocol to find them again; on an account whose shells are stored server side they were deleted for every browser at once. The terminal now reconnects and reattaches, and only forgets a service when its shells are known to be over.
The preconfigured Windows installer is only offered when its settings fit a name Windows will not cut. The length was checked against the 255 characters NTFS allows for one name, but MAX_PATH covers the whole path, so a name that fit arrived truncated — and because the settings live at the end of it, the client then started with no server configured and said nothing. The relay is left out of the name as well, since hbbs tells every client which relay to use; it is still shown on the page and in the config string.
The PowerShell install command asks for administrator rights instead of needing them, and stops when the prompt is refused. RustDesk applies --config only when it is installed and elevated, and unelevated it prints one line and exits, which looked exactly like success. It also installs only when RustDesk is missing, and asks first: an existing installation of any kind — the EXE, the MSI, winget, a per-user copy — now just gets the settings, instead of a failed install over it.

Navigation Menu