Repository navigation
Open
Security
1 / 11 of 1 issue completed
Copy link
Labels
Description
🤖 Generated by the Agentic Engineer
Evidence
create-release's two release jobs hold the release App token and runharden-runnerwithegress-policy: audit, which records outbound connections and blocks none (parent Block unlisted egress in the catalogue's credential-holding publish and release jobs #628).- Measured on 2026-11-12 from StepSecurity's public run insights: across 12 successful release runs in 5 consumer repositories (ksail, platform, go-template, world-at-ruin, wedding-app), the ordinary
Releasejob reached onlygithub.com:443,api.github.com:443andregistry.npmjs.org:443, with telemetry present in every run. The list is on Block unlisted egress in the catalogue's credential-holding publish and release jobs #628. - The protected-source
Releasejob (protected-release: true) did not run in that window, so its list is not measured yet. - Unlike the two publishers, this workflow's revision is not part of a signing identity Platform verifies, so the change needs no other approval.
Audience / problem
Every repository that releases through this workflow, about 20 of them. A compromised dependency or tool inside the release job could send the release token to any host today.
Hypothesis
If both release jobs can run harden-runner in block mode with that three-host allow-list behind a default-off input, a consumer can opt in without writing any allow-list, and an unlisted host is refused with a clear message.
Success signal
One release of a consumer that opted in succeeds in block mode, and a control run proves an unlisted host is refused.
Smallest useful change
- Add a default-off
workflow_callinput (for exampleblock-egress: false) that switches both release jobs toegress-policy: blockwith the measured allow-list kept in the workflow beside the step. - Measure the protected-source job first (one protected release run, or the insights of the next one), and add anything it needs to its list.
- Leave
offline-testand every consumer's default unchanged.
Acceptance criteria
- Both release jobs run in
blockmode when the input is set and inauditmode otherwise; both states are covered by a test. Verified: feat(create-release): let callers block unlisted release egress #913 run 43333781613 at merged head505123d6(block job 131585571108, audit job 131585571207, both success). - A test proves an unlisted host is refused in
blockmode and the failure names it. Verified: job 131585571108 refusedexample.com(curl exit 7) and harden-runner loggeddomain not allowed: example.com. - One consumer release succeeds with the input set before anything defaults to it.
- Consumers that do not set the input see no change. Verified: ascoachingogvaner (create-release v21.3.3, input unset) published v1.15.3 in run 43456255879 with
egress-policy: audit.
Rough size: S.
Metadata
Metadata
Assignees
Labels
Type
Fields
No fields configured for Security.
Projects
- StatusShow more project fields🫴 Ready
Activity
chore: agent-claim #912 nonce=83474954ed6986537c2f5743f0c8a8f4
test(create-release): execute block mode in fixture mode with an egre…
test(create-release): prove the probe's refusal against an audit-mode…
test(create-release): accept only a refused connection as block mode'…
test(create-release): tie block mode's refusal to harden-runner's den…
devantler commentedon Nov 13, 2026
Progress (PR #913 at 505123d). The opt-in
block-egressinput is implemented and both states were executed in CI:[Test] Create Release - No Issue Side Effects / Release egress probe, job 131585571108): reachedapi.github.com,github.comandregistry.npmjs.org;example.comwas refused (curl exit 7), and harden-runner recordeddomain not allowed: example.com.for that attempt.[Test] Create Release - Dry Run / Release egress probe, job 131585571207): reached all three listed hosts andexample.com.Still open here: a real opted-in release by one consumer, which is the remaining proof before anything defaults to block mode. Check two points in that trial:
uploads.github.com, which the list omits. The measured callers upload none.feat(create-release): let callers block unlisted release egress (#913)
chore: agent-claim #912 nonce=192e88de234015877a12417fc4132c49
devantler commentedon Nov 13, 2026
Progress — last acceptance criterion. #913 shipped the opt-in input in v21.3.0. devantler-tech/go-template#523 (merged 2026-11-13, tracked by devantler-tech/go-template#522) switched go-template's own releases to block mode; generated projects stay in audit mode because they own their release configuration and may need other hosts.
egress-policy: block; App token, checkout, npm and semantic-release all ran; nothing published (notmain).main, run 43379607353 at9d4e0ffa:successin block mode; semantic-release found no releasable change (aci:commit), so no release was created yet.Still open: the release-creation call itself. The next
feat/fixmerge into go-template publishes a release in block mode; its run decides this criterion (success → close; a refused host → revert #523's setting and add the host here).ci(release): refuse unlisted outbound hosts in the release jobs (#523)
devantler commentedon Nov 13, 2026
Status, 13 November ~17:10Z: three of four criteria are met. The last one waits on a go-template release.
505123d6covers both modes. The block-mode probe (job 131585571108) refusedexample.com, and harden-runner named the host. The audit-mode probe (job 131585571207) reached it.egress-policy: audit.mainRelease runs in block mode both succeeded, but neither had a releasable change. There are no open go-template PRs, so the release can't be made to happen sooner.The wait is now recorded as an
outcomeblocker in the body, with theblockedlabel. The card moves from In Progress to Ready, as the board guide prescribes for delivered work waiting on an outside event. When the next go-templatefeat/fixrelease runs: if it publishes, close this issue. If a host is refused, revert go-template#523's setting and add that host here.