Default deny GPIO access
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- authorization, embedded-iot, security
Research direction
Start by locating the existing rego policy and the GPIO access definitions; the issue does not name specific files or tests. Determine how compartment permissions are currently represented, then verify that GPIO is denied unless a compartment explicitly grants access.
Written by the indexing model from the issue text.
Description
Is there a way to default deny the GPIO access through the rego unless you explicitly define that the compartment has access to it?
- Dominant language
- C++
- Stars
- 14
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 lowRISC/sonata-software
-
enhancement
lowRISC/sonata-software#81 · 3 comments · 1 assignee ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
lowRISC/sonata-software#77 · 2 comments ·
All issues in lowRISC/sonata-software
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·