Skip to content

[Codex Security] Enabling SSTV can build a moving QSSTV branch as root on the target - #8

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

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

Conversation

@EmDecay

@EmDecay EmDecay commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

QSSTV source builds now run unprivileged and promote only checked artifacts.

  • Git checkout, qmake, make, and ldd run as a locked system account instead of inherited play-level root.
  • Mutable refs no longer refresh by default; explicit updates require and verify a full commit ID.
  • Binary, desktop entry, and icon promotion reject symlinks or wrong ownership, verify SHA-256 identity, and install atomically.
  • Existing sstv-rx and sstv-workstation include paths, install flags, launcher path, and operator execution remain intact.
  • Repository QA now guards the privilege, ref, and artifact invariants against regression.

Static Verification Checks

  • Build privilege boundary (Passed) — Static inspection of tasks/main.yml, without runtime checks, shows Git, qmake, make, and ldd lack root authority.

  • Mutable update pinning (Passed) — defaults/main.yml disables refreshes, while source-ref validation permits updates only for full commit IDs, blocking moving-ref convergence.

  • Artifact promotion boundary (Passed) — promote-artifact.yml rejects symlinks and ownership mismatches, compares SHA-256 digests, then atomically installs artifacts, preventing privileged dereference bypasses.

  • Default install continuity (Passed) — defaults/main.yml retains the HRV repository and initial main ref while disabling refreshes, preserving first-install behavior.

  • Caller behavior preserved (Passed) — sstv-rx and sstv-workstation still include qsstv-runtime behind existing install flags, preserving opt-in QSSTV deployment.

  • Regression assertions retained (Passed) — scripts/qa.py asserts non-root execution, immutable update IDs, no-follow staging, and checksum matching, protecting the boundary.

  • Finding: acf_74a4b030b60e7a53897a68b2f9d77164

  • Patch: arp_ae2e4acbb9c774244452504c2d529b84

  • Base commit: 0ffb68937bc72420999f9d67bc8af90feb1ef617

  • Patch SHA-256: 564d60dae831e059b33809de61352654d996438675f9769b48c64e99300b44d9

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