CortenDesk 0.9.7

Bug-fix release. No migrations — upgrading is a pull and a restart.

Fixed

Editor dialogs could not be scrolled. On shorter screens the Add/Edit Strategy dialog ran off the bottom of the window with no way to scroll, putting the save button out of reach — so a strategy could not be created at all. The same applied to the user, group, role, invitation, device and API token dialogs; Strategies was simply the tallest and the first to hit it.

Whitespace in the RustDesk server key. id_ed25519.pub is written without a trailing newline, so a key pasted through an editor or a compose heredoc often picked one up. The key is compared exactly, so an untrimmed key failed in a way indistinguishable from a genuinely wrong one — clients just would not connect. The public key, ID server and relay server are now trimmed on input.

Added

Strategies: Auto update (allow-auto-update) — push the client's auto-update setting from the console. Note the client only exposes this on installed Windows, and on installed macOS that is not a custom build; on Linux, portable installs and custom-branded builds the toggle is hidden, so setting it may have no visible effect.

Strategies: clearer label. "Let the connecting side change this device's settings" is now "Enable remote configuration modification", matching the client's own wording — the option already existed, but nobody searching for the client's term could find it. Thanks to @dragonidium11 for both suggestions (#11).

DemoSeeder — populates an evaluation install with sample devices, users, groups, address books and log history:

php artisan db:seed --class=Database\\Seeders\\DemoSeeder

Documentation

The wiki has been reorganised and expanded: a page per feature, a full settings reference, a command-line reference, reverse-proxy examples for Caddy, Traefik and nginx, a guide to standing up hbbs/hbbr in Docker, and troubleshooting.

README corrections: the SSO fallback description was wrong (password sign-in returns if SSO is disabled or incompletely configured, but not merely because the provider is unreachable — use CORTENDESK_OIDC_DISABLED=true for that), the WebSocket bridge section now distinguishes Docker from manual installs, and the trusted-proxy note explains that getting it wrong can lock users out via the per-address sign-in limiter.

Upgrading

docker compose pull && docker compose up -d