Repository navigation
Catalog schema v3 release signatures (v0.13.0 Track 95) - #41
Merged
Merged
Conversation
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>
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.
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 viaaead.dev/minisign(plain Ed + prehashed ED, streamed), cosign-blob via PEM ECDSA/Ed25519 keys (stdlib only), gpg viaProtonMail/go-cryptodetached sigs (armored or binary). Both crypto deps were already in the module graph — promoted to direct requires, nothing new added.catalog_versionnow 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)..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 realInstallpath; tampered sig/wrong key/missing sig file all fatal;SignatureURLexpansion; v3 emission; schema-gate rejectionsgolangci-lint run --build-tags goolm,stdjson ./pkg/modules/...— 0 issues (v2.13.2)scripts/lint-docs.sh— OKGenerated with Devin