Skip to content

test: qualify process isolation Tasks 3 and 4 on funded runners - #9

Draft
ORESoftware wants to merge 4 commits into
mainfrom
certify-proc-isolation-12-13-185
Draft

ORESoftware wants to merge 4 commits into
mainfrom
certify-proc-isolation-12-13-185

Conversation

@ORESoftware

Copy link
Copy Markdown
Contributor

Exact-head funded carrier for portfolio Tasks 3 and 4.

Source pins:

  • ORESoftware/ores-proc-isolation-cli#12 — 28a29bbbd75acf4531e973d2c8ec92b68659375d
  • ORESoftware/ores-proc-isolation-cli#13 — b496a4b9d815d41684d4049508020395f763f665
  • ORESoftware/ores-compose#185 — d93a4108849ba37bbca155a8bb679abd2ab8b60f

The carrier uses TEST_FLEET_READ_TOKEN to check out the actual private source commits, so this does not rely on source mirroring.

Qualification:

  • Linux: compile/lint/contracts, permitted external egress, denied host file/loopback/non-loopback interface/nested user namespace, explicit Slirp death with fail-closed tenant termination, explicit tenant death with network-helper cleanup, and no lingering helper IPC/resources.
  • macOS isolation: exact same UID, denied host process probe, denied host file, strict external fail-closed, allowed local workspace/child process, denied outside + symlink-escape writes, and explicit local-loopback mode.
  • macOS ores-compose: actual PR test: prove current Node live-mutex dev with nine clients #13 isolation binary with PR #185, instrumented wrapper around the real binary to capture every generated policy, two-service build/start/child/health workflow, graceful shutdown, second-cycle restart, no outside/symlink writes, and required / auto / off selection checks.

This is supplemental cross-org evidence and does not override native source-repository required checks, which currently cannot acquire runners.

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.

2 participants