Skip to content

docs(signing): tidy the signing-key doc and README install steps (#4) - #6

Merged
dev-montimage merged 1 commit into
mainfrom
docs/4-tidy-signing-doc
Nov 17, 2026
Merged

dev-montimage merged 1 commit into
mainfrom
docs/4-tidy-signing-doc

Conversation

@luongnv89

Copy link
Copy Markdown
Contributor

Closes #4.

Changes

  • docs/signing-key.md: every acceptance criterion of Tidy the signing-key doc and README install steps after #3 #4: the subkey export writes apt-signing-subkey.asc; the --passwd "No secret key" / exit 2 note; rotation sets SUBA/SUBB to the new subkey and gives the subkey B equivalents; the keyring re-download rule covers every key change; the .rev copy is kept apart and is imported after the published keyring on a fresh machine; the mmt-dpi signing-key.asc is exported with --armor.
  • New First-time setup section. The doc pointed to a procedure that was not in the repo. The setup order is: keyring PR, then the apt-signing values, then merge, because a partial setup fails by design.
  • Key model: the primary key now lives on the maintainer's designated signing machine (encrypted disk, dedicated GNUPGHOME, off-machine backup), never in CI. This replaces the offline-drive plan recorded in Add apt/deb package support for mmt-dpi mmt-dpi#24.
  • README: apt-get update first, mktemp instead of a fixed /tmp path, CI wording aligned with AGENTS.md.

Verification

  • Ran the procedure with a throwaway key shaped like the real one. --passwd exits 2 and prints error changing passphrase: No secret key; the export then signs with the CI passphrase and not with the primary one.
  • Ran scripts/sign-repo.sh with that export in ubuntu:24.04. gpgv accepted the InRelease and Release.gpg signatures from the expected subkey. A later index check failed only because the fixture tree had no indexes.
  • A .rev import fails with can't locate keyblock until the public keyring has been imported.

- 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.
@dev-montimage
dev-montimage merged commit f42a282 into main Nov 17, 2026
7 checks passed
@dev-montimage
dev-montimage deleted the docs/4-tidy-signing-doc branch November 17, 2026 14:21
luongnv89 added a commit that referenced this pull request Nov 17, 2026
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
with `export-minimal`.
- Primary: `Montimage Release Signing <developer@montimage.eu>`, `2163
0C36 2624 FB20 5C3D 0B18 4F95 AECC FEF4 8443`, certify-only, expires
2031-11-16.
- Subkey A (APT): `9383150437FEF6B9BCC61DC013D801774F5BF0EB`, expires
2028-11-16.
- Subkey B (tarball): `495827E653092A1F6760ABBC054C7A5FC3824811`,
expires 2028-11-16.
- `docs/signing-key.md#fingerprint` and 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-signing` values (`APT_SIGNING_KEY`,
`APT_SIGNING_PASSPHRASE`, `APT_SIGNING_FINGERPRINT`) are set before this
merges. The run on `main` then signs, verifies against this keyring,
deploys and runs the live smoke tests.

---------

Co-authored-by: MI Dev <developer@montimage.eu>
Co-authored-by: Montimage <developer@montimage.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tidy the signing-key doc and README install steps after #3

2 participants