Redesign tests G62, G72, G80 and G83
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- operating-systems, security
Research direction
Read SECURITY.md and inspect tests G62, G72, G80, and G83 to see how each suspends the guard through a new handle. Find a test design that reaches those same states without using a handle the guard denies. Done means all four tests exercise the intended states without requiring an elevated caller.
Written by the indexing model from the issue text.
Description
These four tests suspend the guard through a new handle to it. The guard denies that by design (SECURITY.md), so they pass only for an elevated caller. They need a design that reaches the same states without a handle the guard refuses.
- 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 77/100
near/near-sdk-rs#1676 ·
Maintainers usually reply within 2 days
-
auto:producer auto:security
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
fritzprix/libr-agent#2595 ·
Maintainers usually reply within 1 day
-
area:fs type:fix
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Tripstack-Corp/spyc#1002 ·
Maintainers usually reply within 1 day
-
github_actions security
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1815 ·
Maintainers usually reply within 1 day
-
[Detail Bug] Request logs can be forged via control characters in fetch object keys (log injection)Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
s2-streamstore/cachey#211 ·
Maintainers usually reply within 1 day