v1.7.1

Docker Commander 1.7.1 is a security follow-up. We switched on GitHub's CodeQL code scanning only after 1.7.0 had shipped, so its first scan ran against a released version. This release fixes what it found, and from now on every change is scanned before it ships.

Security

• The SSH host-key probe no longer signs in. Clicking Test while adding an SSH host used to go on and authenticate to a server nobody had approved yet, which showed it every public key in your SSH agent and default key files. It now stops right after taking the host key.
• A symlink can't redirect file operations outside their folder. Project and template files, imports, the recovery export, backup and restore, and the folders a remote deploy copies now all go through Go's os.Root. A link swapped in mid-operation, for example by a container that has the project folder mounted, is refused at the moment of use.
• The logout cookie is Secure on HTTPS, like the session cookie it replaces.
• The CI and Homebrew workflows run with a read-only token.

Fixed

• --backup names a linked projects/ folder (or the template or revision folder) in its report, including one whose disk is unplugged, instead of leaving it out silently.

Changed

• A new README: a short landing page with what Docker Commander is for, the features at a glance and a quick start. The details moved into the manual: Installing, Configuration, Docker versions, Security model and Architecture.
• New screenshots: deploy preview and deploy history in the README; project secrets, domains and Top talkers in the manual.
• Go, npm and GitHub Actions dependency updates (minor and patch only).

Before you upgrade

• --restore --force won't write through a symlink in the data dir that points outside it. If projects/ lives on another disk through a link, restore into a fresh data dir and move the folders over afterwards.

Full changelog: CHANGELOG.md