Repository navigation
fix(prime): verify signed publications in Electron - #641
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 18, 2026
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This branch was successfully deployed
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.
Installed Nightly reports that no managed Prime publication exists because Electron/BoringSSL rejects the implicit digest used by TUF and Sigstore (
NO_DEFAULT_DIGEST). The same packaged verifier succeeds under regular Node.Patch the pinned verification dependencies to specify Node/OpenSSL's existing SHA-256 default for EC/RSA keys. Preserve explicit algorithms, Ed25519/Ed448 behavior, signature thresholds, provenance policy and rejection of invalid signatures. This enables the existing supported managed installation flow; it does not change a user's selected runtime or clear ownership quarantine.
Validation: 48 focused tests pass, including real cryptographic signatures and tampering checks with Electron's missing-default behavior simulated; targeted lint and formatting pass. Executed the patched source with the installed Electron 44.1.0 / Node 24.19.0 binary against the actual immutable publications: stable sequence 3 and preview sequence 22 both verify source
3694cfef31d29a38757678cafe74e4705ae95662. The unpatched packaged code fails in that same executable. A standalone process in the actual Electron runtime also passed 12 valid/tampered ECDSA, RSA and Ed25519 signature/metadata assertions against the patched installed dependencies.Refs #557. Model: GPT-6; harness: Codex in Pylon Nightly.