Skip to content

[FEATURE] Verify ML-DSA signatures embedded in provider docs (x-stackql-signature), replacing .sig sidecars #856

Closed

Description

@jeffreyaven

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

Sequence and dependencies

  1. 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.
  2. any-sdk: verify + fallback, release ([FEATURE] Verify ML-DSA signatures embedded in provider docs (x-stackql-signature), with .sig fallback any-sdk#153).
  3. stackql: bump, config, docs, release. Unblocks the registry dropping .sig files ([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

Activity

  1. added
    enhancementNew feature or request
    goPull requests that update go code
    on Oct 21, 2026
  2. jeffreyaven commented on Oct 23, 2026

    @jeffreyaven
    MemberAuthor

    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.

  3. jeffreyaven commented on Oct 23, 2026

    @jeffreyaven
    MemberAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestgoPull requests that update go code

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions