Skip to content

Keep PHP CI host launchers outside writable container mounts #344

Open

Description

@rmcdaniel

The admitted PHP CI launcher exposes its repository root and complete host-wrapper state read-write to same-UID package/application code. Such code can replace the host php/Composer wrapper or its launcher target and substitute the next nominal verifier. Security placed activation on HOLD in shared297. No compromise is inferred.

Owner: sample-app. This applies to already-merged main 799df847137dafd3fb70968c94ae56609a313479 as well as the product-tuple draft #339, whose merge/publication is held. General has been notified that the existing exact runtime admission must be held/replaced. The host-Python isolation correction in #342 remains in place; this is the separate writable-control boundary.

Acceptance:

  • Repository/control paths and the complete wrapper/state authority are read-only in PHP containers. Permit only named data/cache/output mounts needed by existing callers; keep PHP playground writes separate from host Python/Rust source.
  • Preserve both PHP minors, every existing caller cell, immutable image identity, resource limits, environment/credential allowlist, fixed-APT checks, CA handoff and live Composer guard.
  • Add marker-only overwrite/rename replacement controls that demonstrate the predecessor escape and refuse on corrected source. Prove intended data writes and the next genuine PHP/Composer verifier still work in actual retained PHP 8.4/8.5 images.
  • Retain actual TLS accept/refuse controls, qualify the original app/audit/playground callers, obtain Security review and the corrected exact central runtime binding before activation.

Source candidate: draft #349, exact f069b118886f922e979d865d964ed5179b9bc3dc, implements the owned defensive remediation. Checkout/control state are read-only; only named vendor/cache/storage/environment/PHP scaffold data and disposable public snapshots are writable. PHP temporary data is separate from host command inputs. Seven explicit fake-Docker command-construction contracts, shell/Python syntax, whitespace, public-boundary and credential/private-path checks pass. No actual container, marker-replacement probe, package/application caller or TLS/runtime qualification ran. The old blocked validation WIP is retained separately and is not wired into this candidate.

Independent Security source review passed for exact f069b118886f922e979d865d964ed5179b9bc3dc. The permitted defensive source remediation and its independent source review are complete, with no source correction requested. Keep this exact candidate frozen and draft. Remaining acceptance is the actual boundary/TLS/application qualification and corrected admission, which are still unperformed under the existing explicit stop. Source inspection/syntax/contract checks do not qualify the runtime. The stopped boundary validation, marker probes, package/app and installed/onboarding execution remain set aside; no replacement caller is admitted. There is no additional routine General approval wait. Any later execution requires an actually permitted operation and normal review; source review does not lift the existing stop.

PR #346's reviewed source is not installed delivery. Preserve its merge/publication hold, frozen #339 candidate 2bf6f2a, and this issue's full acceptance criteria. No rolling tuple refresh is selected. Work on other actionable Sample requirements may proceed independently. A later execution path would need an actually permitted operation and its normal review; source review does not lift the existing stop.

Activity

  1. rmcdaniel commented on Nov 13, 2026

    @rmcdaniel
    MemberAuthor

    The container-boundary validation step is policy-blocked in this session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions