Repository navigation
docs(security): publish signing public key + verification recipe - #7
Merged
Merged
Conversation
- SECURITY.md: standard GitHub security-policy file. Verification recipe (openssl dgst -verify against the split .signed.bin), key-rotation policy, explicit out-of-scope list (MQTT TLS setInsecure, open web UI, no OTA brute-force protection), pointer to GitHub security advisories. - docs/signing_public_key.pem: the public half of the current release signing key, committed so users can verify without reaching for a key server or pinging the maintainer. - README: new "Verifying releases" section with the one-liner recipe. Public keys are safe to commit; the private key lives only in the SECRET_RSA_KEY repo secret + the maintainer's local backup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
SECURITY.mdwith the openssl verification recipe, key-rotation policy, and a scope section calling out the known out-of-scope items (MQTT TLS setInsecure, open web UI, etc.)docs/signing_public_key.pem— the public half of the current release signing keyTest plan
openssl dgst -verify docs/signing_public_key.pem ...matches the recipe in SECURITY.md for v0.1.1's signed binary (already verified locally — this PR just puts the recipe + key where downstream users can find it)🤖 Generated with Claude Code