Repository navigation
Closed
Labels
enhancementNew feature or requestNew feature or requestgoPull requests that update go codePull requests that update go code
Description
Companion to stackql/stackql-provider-registry#482, stackql/any-sdk#153 and stackql-labs/omnisdk#17. The registry is moving provider-doc signing to ML-DSA (FIPS 204, crypto/mldsa, Go 1.27) with the signature hex encoded inside each doc under x-stackql-signature, and will stop shipping .sig sidecars. stackql and any-sdk need to verify the new form. Verification is off by default today (verifyConfig.nopVerify: true, inferred in internal/stackql/cmd/root.go), so this is low risk for existing users.
NOTE: Must be compliant with at least FIPS 204.
What changes
- any-sdk ([FEATURE] Verify ML-DSA signatures embedded in provider docs (x-stackql-signature), with .sig fallback any-sdk#153)
internal/anysdk/registry.go:getVerifiedDocBytesfetches<doc>.sigand callsedcrypto.VerifyFileFromCertificateBytes. New path: if the doc carriesx-stackql-signature, pop it, canonicalise the rest (RFC 8785 JSON via the shared registry package),mldsa.Verifyagainst the embedded public key selected bykid. If absent, fall back to the.sigpath during the transition. - Dependency: bump
github.com/stackql/stackql-provider-registry(nowv0.0.2-alpha01) to the release that shipssigning/pqsig.go 1.27in any-sdk and stackqlgo.mod(stackql 1.25.3 and any-sdk 1.26.10 today). - stackql: bump any-sdk.
verifyConfiggainsallowLegacySig(default true during the transition, later false).nopVerifydefault unchanged; flipping it is a separate decision under [SECURITY] Define and enforce registry content verification before installation and execution #832. - stackql-provider-tests:
signedmode exercises the new path.
Sequence and dependencies
- Registry package release ([FEATURE] Quantum-safe provider doc signing: ML-DSA via crypto/mldsa, signature embedded in the doc, drop .sig sidecars stackql-provider-registry#482, step 1). Blocks this issue.
- any-sdk: verify + fallback, release ([FEATURE] Verify ML-DSA signatures embedded in provider docs (x-stackql-signature), with .sig fallback any-sdk#153).
- stackql: bump, config, docs, release. Unblocks the registry dropping
.sigfiles ([FEATURE] Quantum-safe provider doc signing: ML-DSA via crypto/mldsa, signature embedded in the doc, drop .sig sidecars stackql-provider-registry#482, step 3).
Notes
- Verification stays at doc-read time. Archive pull remains unverified; that is [SECURITY] Define and enforce registry content verification before installation and execution #832's scope, not this issue's.
- Canonicalisation must come from the shared registry package, never reimplemented here, or signatures will not match.
- omnisdk is replacing any-sdk. Verification must exist in whichever SDK stackql routes registry reads through at cutover; the omnisdk side is [FEATURE] Verify ML-DSA signatures embedded in provider docs (x-stackql-signature) when opening a registry tree stackql-labs/omnisdk#17.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestgoPull requests that update go codePull requests that update go code
Activity
jeffreyaven commentedon Oct 23, 2026
Coordinated implementation is in #869, with stackql/any-sdk#155, stackql-labs/omnisdk#23, stackql/stackql-provider-registry#487 and stackql/stackql-provider-tests#2.
The maintainer-approved final protocol is Go stdlib ML-DSA-65 with strictly framed raw-v1 signatures over exact document bytes, not RFC 8785 canonical JSON. The 1,968-document audit found YAML aliases and large integer schema values that must be preserved. Legacy verification is removed; verification remains opt-in. Archive authentication and freshness/rollback controls remain outside this migration (#832).
Merge provider-tests first, the two SDK PRs in parallel, then StackQL. Publish the new StackQL binary and ensure the provider-test downloader obtains it BEFORE merging the registry cutover last. Full platform/Robot CI is being validated; no tests are being skipped to make it pass. PR #869 closes this issue automatically on merge.
jeffreyaven commentedon Oct 23, 2026
Final validation is green: all 37 StackQL PR checks passed at 77ffd37, including the complete native, WSL, Docker and PostgreSQL-sharded Robot matrix. All four companion PRs are green too. Evidence: https://github.com/stackql/stackql/actions/runs/40026926182. Required maintainer approvals and the documented SDK -> StackQL binary release -> registry cutover ordering still apply. This issue is natively linked to close on merge of #869.