Repository navigation
fix(safe): register the release signing keychain before building - #33
Open
paulsenon-r wants to merge 1 commit into
Open
paulsenon-r wants to merge 1 commit into
paulsenon-r wants to merge 1 commit into
Conversation
paulsenon-r
marked this pull request as ready for review
November 12, 2026 07:11
codesign cannot resolve the imported private key outside the user keychain search list, even with --keychain. Preserve existing search entries and check identity validity plus a binary signing probe before exporting the release identity. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
paulsenon-r
force-pushed
the
safe/fix-signing-keychain
branch
from
November 12, 2026 08:54
a8be0f5 to
7cee1e3
Compare
This branch has not been deployed
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.
Problem
The first signed release failed in run 43170295251 after certificate import and fingerprint verification succeeded.
codesigncould not resolve the private key from the temporary keychain.Change
Register the temporary signing keychain in the user search list, preserving existing entries. On this Mac,
--keychainalone did not make the identity available tocodesign.Before exporting the release identity, require its SHA-1 in the valid code-signing identities and sign/verify a temporary binary. Failed probes stop the job before the build; the probe and PKCS#12 are removed on exit.
The current PKCS#12 encoding and secrets remain usable. Certificate pinning, the runner-only trust step, the Electron signer, and release triggers are unchanged.
Scope and approval
Follow-up to #17 and #31, limited to the signed-release key lookup failure and early detection. Includes five isolated regression cases in PR checks and the corresponding reviewed network-baseline fingerprints.
Verification
find-identity.no identity found.-legacyimported successfully. No secret regeneration required.sudo, are faked in these tests.workflow-scan.ts origin/main,policy-verify.ts, andegress-scan.ts.apps/mobile/scripts/upload-sourcemaps.mts,apps/web/scripts/verify-built-boot.ts, andscripts/safe/sign-macos.cjs. Used the authorizedVP_GIT_HOOKS=0bypass for the commit..pak; direct signing of a non-code resource succeeded. No resource-skipping change is needed for this failure.The full Electron build and the runner's system-trust step were not rerun locally. No workflow dispatch, merge, secrets, or environment changes.
Implementation ran through the Codex harness with GPT-6.1 Sol.
🤖 Generated with Claude Code