Repository navigation
Package ForgeBox offline firmware signing tools - #145
Draft
3rdIteration wants to merge 1 commit into
Draft
3rdIteration wants to merge 1 commit into
3rdIteration wants to merge 1 commit into
Conversation
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.
What changes
The build PC prepares a ForgeBox OTA with the official CLI compressor and puts a small signing request on microSD. SeedSigner derives a dedicated BIP85 secp256k1 key, returns the two OTA signatures, and the PC verifies and assembles the update against the original image and trusted public key. The optional USB bridge also supports offline proof of possession for initial registration.
The build installs the Python signer alongside the existing OS signing tools for Pi, La Frite and Luckfox. It uses the existing embit and python-ecdsa packages. The app PR adds the review and authorization screens.
Validation
Physical registration, nonce lifetime and flashing need device validation. The signer authorizes digests and relies on the operator to review the firmware on a trusted PC. Pure Python ECDSA does not guarantee constant-time execution or memory erasure.
Paired app change: SeedSigner #488.