Skip to content

Restrict updater tokens to trusted HTTPS hosts - #228

Merged
LuisPalacios merged 1 commit into
mainfrom
fix/164-updater-token-host-gate
Nov 14, 2026
Merged

LuisPalacios merged 1 commit into
mainfrom
fix/164-updater-token-host-gate

Conversation

@LuisPalacios

Copy link
Copy Markdown
Owner

Closes #164

What changed

  • Send the updater token only to five exact GitHub hosts over HTTPS.
  • Apply the same redirect policy to release checks and downloads, strip authorization after an unsafe hop, and preserve caller redirect behavior.
  • Keep the signing key and fail-closed verification unchanged.

Test plan

Interactive smoke testing remains required before merge.

Preserve redirect policies while stripping authorization across unsafe hops for release checks and downloads. Cover exact hosts, downgrade redirects and caller redirect behavior with isolated tests.

Closes #164
@LuisPalacios
LuisPalacios force-pushed the fix/164-updater-token-host-gate branch from bcd5c88 to 3a6956d Compare November 14, 2026 09:44
@LuisPalacios
LuisPalacios merged commit 915258f into main Nov 14, 2026
3 checks passed
@LuisPalacios
LuisPalacios deleted the fix/164-updater-token-host-gate branch November 14, 2026 09:49
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.

[Phase 1] Send GITHUB_TOKEN only to GitHub hosts in the updater

1 participant