Conversation
Record the validated native macOS GCC 14.2 build baseline. Add sanitized findings, evidence, and disclosure documentation. Ignore the visible local review-private workspace.
Zartharas
marked this pull request as ready for review
August 5, 2026 01:05
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
This change establishes the WP1 reproducible firmware-build baseline for Monstatek M1.
It:
SOURCE_DATE_EPOCHfrom the source commitMotivation
The repository previously lacked a fully documented, repeatable canonical firmware-build path.
The new container workflow provides a stable Linux/amd64 environment and records sufficient metadata to identify the source, build definition, toolchain, image, and resulting release artifacts.
Validation
The finalized build definition was validated at commit:
8c5e4f2401e37593281ffde490f657ba05b061a2Two clean builds from that exact commit produced:
SHA256SUMSValidated image identity:
sha256:127f9407e8f8bb9a2c5f811597a51dbfe9eeab558b82bd030ff1f3c086ac4bfaValidated artifact hashes:
MonstaTek_M1_v0800.bin433790ee249a574a58d60281fc5da09e72debb05bd478283bd912e1a3434d176MonstaTek_M1_v0800_wCRC.bin7101bb1511dd63fcc54298f0befdc991a84f25bce53208a6c3bf8ebe7ac45202MonstaTek_M1_v0800.elfcaa8c8b1882d49122fc5d4340c38b269a0fc230ef6500cb15f7f9838a0ccc64aMonstaTek_M1_v0800.hex22706a7ba1373a348d67fc1651bd76220c86ff4860923e3717799eed87aa57e4Additional validation included:
elf32-littlearmarmv8-m.main470536 / 7032 / 169872Current limitations
This PR does not claim:
The Debian base-image digest and Arm GNU archive are pinned. Debian packages installed through
apt-getare not yet individually version-pinned or obtained from a dated repository snapshot.The native and container builds are valid firmware builds but are not byte-identical. The container workflow is therefore documented as the canonical reproducible-build path.
Repository hygiene
Generated build outputs and raw compiler/Docker logs are not introduced by this PR.
Raw validation logs remain local because they contain host-specific diagnostic paths. The committed evidence file contains only sanitized identities, hashes, sizes, and validation outcomes.