Support non-legacy receipt signature verification#217
Merged
Conversation
…s, CI - lib/verifyReceipt.js: accept proof.canonical || proof.canonicalization; accept sig/kid from signature.* or metadata.proof.*; add verifyCanonicalSignature for v1.1.0 raw-bytes path; dual-mode routing by hash_sha256 presence so legacy receipts continue to pass; relax schemaValid hash_sha256 requirement - api/_receipt-model.js: fix proof.alg check ed25519-sha256→ed25519; fix canonical field lookup canonical_id→canonicalization - .github/workflows/ci.yml: new CI running npm test on push/PR - .env.example: document RUNTIME_BASE_URL
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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
This PR adds support for verifying receipts using direct canonical string signatures in addition to the existing legacy hash-based verification. It introduces a new signature verification mode that signs the canonical payload directly instead of its SHA256 hash.
Key Changes
verifyCanonicalSignature()to verify signatures against the canonical string directly using Ed25519receipt.metadata.proof) and flat (receipt.signature) structuresed25519-sha256toed25519in runtime metadata validationcanonicalandcanonicalizationokresult to only requirehashMatchedin legacy mode, allowing new mode receipts to pass without hash validation.env.examplewith runtime base URLImplementation Details
hash_sha256in the proof metadata (isLegacyModeflag)verifyHashHexSignature()orverifyCanonicalSignature()based on the modehttps://claude.ai/code/session_0112Taq5ne2BieC3hfqjjf3r