Repository navigation
feat(apt): publish the Montimage release signing key and go live - #7
Merged
Merged
Conversation
- signing-key.md: the subkey export writes to a file the next step imports; note that --passwd on the stub primary exits 2 with "No secret key" and the subkey is still re-protected; rotation sets SUBA/SUBB to the new subkey and gives the subkey B names, files and secrets; the "download the keyring again" rule covers every key change; the .rev copy is kept apart and, on a fresh machine, imported after the published keyring; mmt-dpi's signing-key.asc is exported with --armor. - Add a First-time setup section (create, back up, export, re-protect, publish). Secrets and public key land back to back, since either half alone fails CI here and the release in mmt-dpi. - The primary key lives on the maintainer's designated signing machine (encrypted disk, off-machine backup), not on an offline drive. - Commands ending in '!' quote it, so they paste safely into zsh. - README: apt-get update before installing prerequisites, mktemp instead of a fixed /tmp path, CI wording aligned with AGENTS.md.
Commit the public keyring (primary 21630C362624FB205C3D0B184F95AECCFEF48443, subkeys A and B) as site/montimage-archive-keyring.gpg, publish the fingerprints in docs/signing-key.md and the README, and replace the not-yet-live page with the install steps. With the apt-signing values set, the run on main signs and deploys the repository.
dev-montimage
approved these changes
Nov 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #6: review only the last commit. Once #6 is merged this branch is rebased onto
main.Changes
site/montimage-archive-keyring.gpg: the public keyring, exported withexport-minimal.Montimage Release Signing <developer@montimage.eu>,2163 0C36 2624 FB20 5C3D 0B18 4F95 AECC FEF4 8443, certify-only, expires 2031-11-16.9383150437FEF6B9BCC61DC013D801774F5BF0EB, expires 2028-11-16.495827E653092A1F6760ABBC054C7A5FC3824811, expires 2028-11-16.docs/signing-key.md#fingerprintand the README now print the fingerprint. The dry-run banner is removed.site/index.html: the install steps replace the "not yet live" page.Go-live order (docs/signing-key.md, First-time setup step 4)
The three
apt-signingvalues (APT_SIGNING_KEY,APT_SIGNING_PASSPHRASE,APT_SIGNING_FINGERPRINT) are set before this merges. The run onmainthen signs, verifies against this keyring, deploys and runs the live smoke tests.