Skip to content

[Codex Security] Compromising the UniPager download origin can replace both its signing key and root package - #6

Draft
EmDecay wants to merge 1 commit into
mainfrom
codex-security/arp_6217624af657a5d549a4666047a21c3f
Draft

EmDecay wants to merge 1 commit into
mainfrom
codex-security/arp_6217624af657a5d549a4666047a21c3f

Conversation

@EmDecay

@EmDecay EmDecay commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

UniPager now requires an independently reviewed signing-key checksum before APT can trust the repository.

  • A new hamstack_unipager_repo_key_checksum must be a literal SHA-256 digest; missing or malformed values fail closed.
  • The key download verifies that digest before signed_by repository configuration and the root package installation.
  • Operators retain custom repository and key URLs, with reviewed rotations performed by explicitly updating the pinned digest.
  • hamstack_unipager_install: false continues to permit service-state management without requiring a checksum.
  • The assessment used static source and diff evidence only; runtime checks were not performed.

Static Verification Checks

  • Pinned key enforcement (Passed) — roles/digital/unipager/tasks/main.yml validates a literal SHA-256 checksum and binds it to get_url, closing same-origin key substitution.

  • Trust boundary ordering (Passed) — roles/digital/unipager/tasks/main.yml places checksum verification before signed_by configuration and privileged package installation, closing the original attack path.

  • Legitimate modes preserved (Passed) — roles/digital/unipager/tasks/main.yml gates checksum enforcement on installation, preserving service management when package installation remains disabled.

  • Rotation contract preserved (Passed) — roles/digital/unipager/README.md documents independent digest review and explicit key rotation, preserving legitimate repository updates.

  • Finding: acf_3aad8b1ad3a40bbd54a7221c5c2d5a61

  • Patch: arp_6217624af657a5d549a4666047a21c3f

  • Base commit: 0ffb68937bc72420999f9d67bc8af90feb1ef617

  • Patch SHA-256: 31b6f8c852b99224cf59834ecd335f38fe55d3398826600c1489bd93106ea34f

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