8000 Catalog schema v3 release signatures (v0.13.0 Track 95) by stpinkie · Pull Request #41 · stpinkie/rhizome · GitHub
[go: up one dir, main page]

Skip to content

Catalog schema v3 release signatures (v0.13.0 Track 95) - #41

Merged
stpinkie merged 1 commit into
mainfrom
devin/track-95-module-trust
Sep 23, 2026
Merged

stpinkie merged 1 commit into
mainfrom
devin/track-95-module-trust

Conversation

@stpinkie
Copy link
Copy Markdown
Owner

Summary

  • ReleasePin.signature — optional {kind, url, key} per release (minisign / cosign-blob / gpg), catalog schema v3. The pinned digest remains the mandatory floor; a declared signature is fetched over HTTPS and verified against the downloaded archive before extraction. Missing = OK, declared-but-failing = fatal.
  • pkg/modules/sigverify.go — three verifiers: minisign via aead.dev/minisign (plain Ed + prehashed ED, streamed), cosign-blob via PEM ECDSA/Ed25519 keys (stdlib only), gpg via ProtonMail/go-crypto detached sigs (armored or binary). Both crypto deps were already in the module graph — promoted to direct requires, nothing new added.
  • Key material is pinned inline in the catalog — the catalog is the trust root (Ed25519-signed or embedded); a remotely fetched key would inherit only TLS trust and could be swapped with the artifact.
  • catalog_version now emits the lowest version covering the content (catalogVersionRequired): still 2 today, 3 only once a release actually declares a signature — older binaries keep working until then. The schema gate rejects malformed declarations (bad kind, missing url/key).
  • Tenant survey: none publish signatures — nimbus-eth1 v0.4.1 and helios 0.11.1 ship bare tarballs; kubo v0.43.1 ships .sha512+.cid (integrity hints, not sigs). Per the sprint plan the track ships mechanism + signed fixtures + documented posture rather than dead fields.
  • docs/design/llama-cpp-module.md — the second deliverable: unscheduled module design covering layout-preserving extraction (install.binary_path), digest-pinned model weights (model_url+model_sha256, HF LFS hashes as the upstream source), the ondemand consumer shape, and the GPU/backend field sketch.

Test plan

  • go build -tags goolm,stdjson ./...
  • go test -tags goolm,stdjson ./pkg/modules/... — fixtures sign real artifacts per kind through the real Install path; tampered sig/wrong key/missing sig file all fatal; SignatureURL expansion; v3 emission; schema-gate rejections
  • golangci-lint run --build-tags goolm,stdjson ./pkg/modules/... — 0 issues (v2.13.2)
  • scripts/lint-docs.sh — OK

Generated with Devin

A release pin may now declare signature {kind, url, key} — minisign,
cosign-blob, or gpg. installRelease still enforces the pinned digest
as the mandatory floor, then fetches the declared signature over
HTTPS and verifies it against the downloaded archive with the
catalog-pinned key. Missing signature is fine; declared-but-
unverifiable is fatal before extraction.

- sigverify.go: per-kind verifiers — minisign (aead.dev/minisign,
  both Ed and prehashed ED), cosign-blob (PEM ECDSA/Ed25519 keys,
  base64 or raw sig), gpg (ProtonMail/go-crypto detached sigs,
  armored or binary). Both deps were already in the module graph.
- Key material is pinned inline in the (signed/embedded) catalog:
  a remotely fetched key would inherit only TLS trust.
- catalog_version now emits the lowest schema version covering the
  content — 3 only when a signature is actually declared, so older
  binaries keep working until a signed release ships. The schema
  gate rejects malformed signature declarations outright.
- Tenant survey: nimbus v0.4.1, helios 0.11.1, kubo v0.43.1 publish
  no cryptographic signatures (bare archives + checksums) — the
  mechanism is pinned by signed fixtures in track95_test.go and the
  posture is documented, per the sprint plan.
- docs/design/llama-cpp-module.md: unscheduled module design —
  layout-preserving extraction, digest-pinned model weights,
  ondemand shape, GPU/backend field sketch.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@stpinkie
stpinkie merged commit 31f87ea into main Sep 23, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0