Moorhold docs

How a release is trusted

A Moorhold server should only run a release that Moorhold signed, and only the files and images that signature covers. That's why every release is published as a set of files on https://get.moorhold.dev/<version>/, with one signature over the lot.

The signed file is the release lock, release.lock. It names the release and pins the sha256 of the Moorhold bundle, of Node for each processor, and of the manifest. The signature is a minisign signature beside the lock. The server trusts a copy of the release key, and an install or an upgrade checks the lock against that key before it uses anything the lock names.

Images come from their registries by the digest in the signed manifest, never by tag. On a server, pulling Moorhold's own images needs your access key, which can download those images and nothing else. The Moorhold app for Mac needs no key.

The list of files, what's in each, and how each is checked is in Release files.