fix(HeavyButter): add SHA-256 integrity verification for App Store downloads#2523
Open
r13xr13 wants to merge 1 commit into
Open
fix(HeavyButter): add SHA-256 integrity verification for App Store downloads#2523r13xr13 wants to merge 1 commit into
r13xr13 wants to merge 1 commit into
Conversation
…wnloads (AV-004) - Add verify_sha256() helper using mbedtls SHA-256 - Add EXPECTED_APPSTORE_SHA256 macro (empty = check disabled) - Verify downloaded App Store script hash before saving to LittleFS - Reject downloads that fail integrity check
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
Adds SHA-256 integrity checking to App Store downloads to prevent tampered scripts from being installed.
Changes
verify_sha256()helper using mbedtls SHA-256EXPECTED_APPSTORE_SHA256build-time macro (empty = check skipped)Security Impact
Before: Anyone who can MITM the HTTP connection (or compromise the server) can inject arbitrary JS that runs with full device permissions.
After: The App Store script hash is pinned in firmware. Mismatched content is rejected. The maintainer sets the expected hash once the server content is verified.