chore: fingerprint signing secrets for cross-repo comparison#31
Open
dinex-dev wants to merge 1 commit into
Open
chore: fingerprint signing secrets for cross-repo comparison#31dinex-dev wants to merge 1 commit into
dinex-dev wants to merge 1 commit into
Conversation
Adds a manual-dispatch workflow that prints SHA-256 fingerprint + byte length for the four mac signing / notarize secrets, salted with a fixed public constant. Output goes to the run's STEP_SUMMARY. Purpose: let dev and prod each fingerprint their own copies of the same logical secrets and compare hashes side-by-side. Same salt + same algo on both repos means equal stored bytes → equal output hashes. Different hashes (or different lengths) prove the stored values diverge — gives us a definitive answer to "are these secrets actually byte-identical across repos" without ever revealing the secret bytes. On dev the workflow reads from BSTACK_APPLE_ID / BSTACK_APPLE_APP_- SPECIFIC_PASSWORD / BSTACK_MAC_CERTS / BSTACK_MAC_CERTS_PASSWORD. Prod's equivalent workflow should reference whatever names prod stores the same logical values under (APPLE_ID / APPLE_APP_SPECIFIC_PASSWORD / BSTACK_MAC_CERTS / BSTACK_MAC_CERTS_PASSWORD per current prod state) — the env var names map the local secret to a stable logical name so the fingerprint table is directly comparable.
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 a manual-dispatch workflow that prints a salted SHA-256 fingerprint + byte length for each of the four mac signing / notarize secrets. Output goes to the run's
STEP_SUMMARY(markdown panel on the run page) so it's easy to grab and compare against the equivalent fingerprint fromrequestly/http-interceptor-desktop-app.This is a debug aid for the question "are the values stored under `APPLE_ID` on prod actually the same bytes as the values stored under `BSTACK_APPLE_ID` on dev?" — the only remaining variable that can explain why mac notarize succeeds here but fails on prod (full code-tree comparison turned up no other differences).
How to use
Why salted
The salt is a fixed public constant (`requestly-signing-secret-fingerprint-v1`). It's not a secret — it just prevents the hash output from being a raw SHA-256 of the secret value, which would in principle be brute-forceable for very weak secrets (not a real risk for Apple credentials, but cheap defense). Both repos must use the same salt for hashes to be comparable, so don't change it.
What it doesn't do
Cleanup
This is a temporary debugging aid. Once the prod / dev secret divergence is identified and fixed, this workflow file can be deleted in a follow-up PR — leaving it in the tree indefinitely is fine but unnecessary.
🤖 Generated with Claude Code