Repository navigation
fix(qualification): reject aliased sealed-copy headers - #834
Merged
Merged
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.
The developer-only sealed-copy guest consumer and independent oracle decoded the 8-byte artifact magic as ASCII, which masks the high bit. A bundle with a high-bit alias of
AEGSIM01and a matching hash could pass the format check and reach guest-copy creation.Compare the exact header bytes in both readers. The focused contract test confirms canonical acceptance, rejects each single-byte alias and the all-byte alias with recomputed hashes, and verifies no guest destination is created.
Validation: focused sealed-import contract suite (9/9), scoped ESLint, Prettier,
git diff --check, independent GPT-6.1 Sol source review. This does not qualify E2.3, protected installation, or VM containment.