Sign each release's SHA256SUMS with the inbuxa suite's minisign key, so a server/relay download can be verified against the public key the docs publish (https://docs.inbuxa.org/install/verifying/) -- the same scheme the installer, cli and migrate releases now use.
This is deliberately separate from the existing relay .sig signing (relay-sign with RELAY_RELEASE_KEY), which the server uses only to let a relay accept a binary as an auto-upgrade. The relay flow is untouched.
Change is to the binaries job in .gitea/workflows/publish.yml only (AGPL CI infra; no SEL-marked source touched): a minisign step after SHA256SUMS is built (Alpine apk add minisign), and SHA256SUMS.minisig added to the attach list. The step no-ops with a warning when MINISIGN_SECRET_KEY is unset, and the attach loop skips the signature if it's absent -- exactly like the three tools.
Before this does anything, MINISIGN_SECRET_KEY must be added to inbuxa-server's Gitea secrets (the same suite key already on installer/cli/migrate; its value is the unencrypted /run/media/john/PROJECTS1/inbuxa-release.key). Suggest adding the secret, then merging, so the first signed server release follows.
Left out on purpose: the release-notes body text still says with SHA256SUMS and doesn't mention the signature, to avoid claiming 'signed' on a release cut before the secret is set. Trivial follow-up once signing is confirmed. YAML validated; both embedded Python blocks compile; no Go changed so CI is unaffected.
Sign each release's `SHA256SUMS` with the inbuxa suite's minisign key, so a server/relay download can be verified against the public key the docs publish (https://docs.inbuxa.org/install/verifying/) -- the same scheme the installer, cli and migrate releases now use.
This is deliberately separate from the existing relay `.sig` signing (`relay-sign` with `RELAY_RELEASE_KEY`), which the server uses only to let a relay accept a binary as an auto-upgrade. The relay flow is untouched.
Change is to the `binaries` job in `.gitea/workflows/publish.yml` only (AGPL CI infra; no SEL-marked source touched): a minisign step after `SHA256SUMS` is built (Alpine `apk add minisign`), and `SHA256SUMS.minisig` added to the attach list. The step **no-ops with a warning when `MINISIGN_SECRET_KEY` is unset**, and the attach loop skips the signature if it's absent -- exactly like the three tools.
**Before this does anything, `MINISIGN_SECRET_KEY` must be added to inbuxa-server's Gitea secrets** (the same suite key already on installer/cli/migrate; its value is the unencrypted `/run/media/john/PROJECTS1/inbuxa-release.key`). Suggest adding the secret, then merging, so the first signed server release follows.
Left out on purpose: the release-notes body text still says `with SHA256SUMS` and doesn't mention the signature, to avoid claiming 'signed' on a release cut before the secret is set. Trivial follow-up once signing is confirmed. YAML validated; both embedded Python blocks compile; no Go changed so CI is unaffected.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Sign each release's
SHA256SUMSwith the inbuxa suite's minisign key, so a server/relay download can be verified against the public key the docs publish (https://docs.inbuxa.org/install/verifying/) -- the same scheme the installer, cli and migrate releases now use.This is deliberately separate from the existing relay
.sigsigning (relay-signwithRELAY_RELEASE_KEY), which the server uses only to let a relay accept a binary as an auto-upgrade. The relay flow is untouched.Change is to the
binariesjob in.gitea/workflows/publish.ymlonly (AGPL CI infra; no SEL-marked source touched): a minisign step afterSHA256SUMSis built (Alpineapk add minisign), andSHA256SUMS.minisigadded to the attach list. The step no-ops with a warning whenMINISIGN_SECRET_KEYis unset, and the attach loop skips the signature if it's absent -- exactly like the three tools.Before this does anything,
MINISIGN_SECRET_KEYmust be added to inbuxa-server's Gitea secrets (the same suite key already on installer/cli/migrate; its value is the unencrypted/run/media/john/PROJECTS1/inbuxa-release.key). Suggest adding the secret, then merging, so the first signed server release follows.Left out on purpose: the release-notes body text still says
with SHA256SUMSand doesn't mention the signature, to avoid claiming 'signed' on a release cut before the secret is set. Trivial follow-up once signing is confirmed. YAML validated; both embedded Python blocks compile; no Go changed so CI is unaffected.