macOS backend
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- macos, rust
- Domain
- operating-systems
Research direction
Start by reading the existing platform guard and shared behaviour tests to understand how the Windows backend fulfills the process tree contract. Then investigate the stated macOS escape cases and the proposed dedicated-user design, including its administrator install requirements. Done means the macOS backend passes the shared tests and 20 repeated escape-test runs with no survivors, and the platform page documents its tier and evidence.
Written by the indexing model from the issue text.
Description
macOS has no backend at 0.5.0, and the guard refuses to build for it rather than make a promise it cannot keep.
Measured on macOS 27: tracking a tree without privilege loses processes. A double fork that leaves the session can escape between fork notices, because a fork notice does not name the child.
The one design found that keeps the promise runs each command as a dedicated user and ends it with kill(-1) as that user. It needs an administrator install that creates a pool of such users. Process coalitions and Endpoint Security also need privilege.
Done when: a macOS backend passes the shared behaviour tests, including the escape tests repeated 20 times, with no survivors, and the platform page states its tier with that evidence.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from WikdSolvemProbler/process-tree-guard
-
good first issue roadmap
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
platform roadmap
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Timing-dependent library test: deep_owner_expiry_after_existing_timer_preserves_native_last_errorOpengood first issue roadmap
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
roadmap
Difficulty 2/5 1-3 hours Newbie friendliness 43/100
-
roadmap
Difficulty 3/5 1-2 days Newbie friendliness 56/100
All issues in WikdSolvemProbler/process-tree-guard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
`nsh-core` fails to compile when taffy's default `calc` feature is enabled elsewhere in the graphOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
longbridge/nsh#966 ·
Maintainers usually reply within 1 day
-
Windows docs: pin a tested ConPTY version for Kitty graphics; 1.25.260930003 corrupts large uploadsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
raphamorim/rio#2021 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
hydro-project/infinity#187 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
near/near-sdk-rs#1676 ·
Maintainers usually reply within 2 days