Make Codex signature normalization reproducible and JIT-safe - #21
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
main15.5.0, 16 KiB signing pages, DER entitlements, and the original identifiersFailure fixed
PR #16 relied on the host default
codesignpage size. The failed macOS 15 run accepted the official source signature, re-signed it with 4 KiB pages, and then disagreed with identities derived on macOS 26, where the default is 16 KiB. The earlier signing command also omitted the two JIT entitlements carried by the officialcodexandcodex-code-mode-hostpayloads.This replacement always normalizes the two exact pinned files. Conditional preservation could ship an upstream signature that succeeds on one builder but is known to fail strict verification on another supported host. Every source package, source file, signing input, output identity, entitlement, structural byte boundary, and reconstruction delta is fail-closed.
PR #15 contributes no code here. Its routing behavior is already present on current
main, while its remaining manifest deletion would weaken compatibility with a published recovery boundary.Local evidence
check:complete: passed, including 3,054 desktop tests, 23 gateway integration tests, and every production buildThis is intentionally a draft until macOS 15 and macOS 26 reproduce the same pinned identities and the full required gate is green.