Repository navigation
Verify the release manifest signature before installing (0.4.2) - #46
Merged
Merged
Conversation
The installer now reads <channel>.signed.json, the manifest text plus an RSA signature over it, and refuses a manifest that no listed release key signed. Checksums in the manifest were already mandatory; this is what makes the manifest itself trustworthy. Verification is RSA PKCS#1 v1.5 with SHA-256 in the standard library, so the package gains no dependency. Co-Authored-By: Claude Opus 5.5 <[email protected]>
ShahriarAhnaf
marked this pull request as ready for review
October 10, 2026 06:53
Co-Authored-By: Claude Opus 5.5 <[email protected]>
ShahriarAhnaf
changed the title
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.
The installer reads
<channel>.signed.jsoninstead of<channel>.json:{"manifest": "<the manifest text>", "signature": "<hex RSA signature>"}and refuses a manifest that no key in
RELEASE_KEYSsigned. Applies tosimantic install, the engine fetched on the firstSim(...), and the Rust engine.RELEASE_KEYSis a list so a key can be rotated; it holds one key today.v0.4.2on the merge commit publishes to PyPI.Ready to release. Signed manifests are live for both products (
cli0.6.9,pyrite0.6.3).Tests
install("sim"),install_engine()andinstall_rust_engine()all verified the signature, checked the checksum and installed. The installedsimreports 0.6.9.🤖 Generated with Claude Code