The one-line installer for Tend and the signed release channels it reads.
curl -fsSL https://get.tend.host/install.sh | sudo bashsite/is exactly whathttps://get.tend.hostserves:install.sh: stage 0, about 150 readable lines. It downloads the channel manifest, checks its Ed25519 signature against the key written inside it, downloads the full installer the manifest names, checks its SHA-256, and runs it.install.sh.sha256,install.sh.sig: its checksum and its signature.compose.yml,compose.yml.sig: the Docker Compose install for people who already run Docker (curl -fsSL https://get.tend.host/compose.yml -o compose.yml && docker compose up -d). It pins the panel image by version and digest, is signed under its own prefix (tend-install-compose-v1) and appears only for a stable release whose image carriescompose.yml.tmpl. Beta never changes it.tend-panel-release-1.pub.pem: the release public key.v1/stable.json,v1/beta.jsonand their.sig: the signed channel manifests. Each pins the panel imageghcr.io/tend-stack/tend-hostby digest and the stage 1 installer by SHA-256, and expires after 30 days.v1/install-panel-<version>.sh: stage 1 for each version a channel names.SHA256SUMS: checksums of all of the above.
- The
channelsrelease carries the same files.install.shfalls back to it when get.tend.host does not answer. panel-v<version>releases keep every stage 1 that was ever published.
Everything in site/ is written by .github/workflows/publish.yml. Nobody edits
it by hand. The code in this repository is maintained in the Tend panel
repository and copied here.
curl -fsSLO https://get.tend.host/install.sh
curl -fsSLO https://get.tend.host/install.sh.sig
curl -fsSLO https://get.tend.host/tend-panel-release-1.pub.pem
{ printf 'tend-install-script-v1\n'; cat install.sh; } > message
base64 -d install.sh.sig > signature.bin
openssl pkeyutl -verify -pubin -inkey tend-panel-release-1.pub.pem -rawin -in message -sigfile signature.bin
less install.sh
sudo bash install.shThe Compose file is checked in one line, with the prefix tend-install-compose-v1:
curl -fsSLO https://get.tend.host/compose.yml.sig && curl -fsSLO https://get.tend.host/tend-panel-release-1.pub.pem && (printf 'tend-install-compose-v1\n'; cat compose.yml) > m && base64 -d compose.yml.sig > s && openssl pkeyutl -verify -pubin -inkey tend-panel-release-1.pub.pem -rawin -in m -sigfile s && rm m sThen compare the key with the SPKI printed in the docs
(MCowBQYDK2VwAyEA6mqh9euEIZV1KSTZzWBJ8xaluXkPBt5GGg+CuNLbuBM=).
A manifest is checked the same way, using the prefix tend-panel-release-v1
instead of tend-install-script-v1. Also check its expires_at and its
channel, as install.sh does.
- A panel release tag, signed with the maintainer's SSH key, is built for
linux/amd64andlinux/arm64by the panel's GitHub workflow, which also publishes a proof: the signed tag object and a Sigstore signature, made by that workflow run, over the statement {version, revision, image digest}. - Every 15 minutes,
publish.ymlcopies a version and its proof to the publicghcr.io/tend-stack/tend-hostby digest, but only if the proof verifies: the tag signature checks againstrelease-tag-signers(the maintainer's pinned key), and the Sigstore certificate names the panel's release workflow, that tag and that commit. Then it reads that package anonymously. Stable takes the highest version without a prerelease part, and beta takes the highest version of all. A beta tag therefore never changesstable.json, and a channel never moves to a lower version. - The version, the revision, stage 1,
install.shand the public key are all read from the image at that digest. - Nobody approves a run; the signed tag is the approval. The
signjob checks the proof again and signs only in thereleaseenvironment. Manifests are re-signed every week, so a valid one is never more than about seven days old. A release whose proof does not verify is refused and never blocks that re-sign. - A refusal, a failed run, or a change to the code on
mainopens a GitHub issue in this repository (one per title; no repeat comments).site/is the only part ofmainthe workflow changes, and it pushes with a deploy key.