Skip to content

Probe macOS TLS stacks for eMudhra chain (do not merge) - #603

Closed
david-crespo wants to merge 2 commits into
mainfrom
emudhra-probe
Closed

david-crespo wants to merge 2 commits into
mainfrom
emudhra-probe

Conversation

@david-crespo

Copy link
Copy Markdown
Contributor

Testing!

@david-crespo
david-crespo deleted the emudhra-probe branch November 3, 2026 02:50
@david-crespo
david-crespo restored the emudhra-probe branch November 3, 2026 02:51
@david-crespo david-crespo reopened this Nov 3, 2026
@david-crespo
david-crespo deleted the emudhra-probe branch November 3, 2026 02:54
david-crespo added a commit that referenced this pull request Nov 3, 2026
I saw actions/runner-images#15228 and went
looking for our workflows where it matters. The macOS runner images
still trust the compromised eMudhra CAs, so `actions/checkout` on macOS
can be intercepted, and it sends `GITHUB_TOKEN`. In most of our repos
that token is read-only on a public repo, so it's not worth much. This
release workflow is the exception: our `macos-15` and `macos-15-intel`
jobs run with `contents: write`.

This PR builds on all four OSes with a read-only token and uploads the
binaries as artifacts. A single `release` job on Ubuntu, which isn't
affected, is the only one with write access, and it publishes all four.
The other download that could have mattered is the toolchain, but a
probe (#603) showed rustup on all four macOS images rejects the chain as
revoked.

I haven't run the new workflow yet. It only runs on version tags or when
a PR has the `release-test` label, so adding the label here should
produce a draft `v0.0.0-pre+<sha>` release with all four binaries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant