[test_security] test access control policies
Open
Nobody has claimed this yet.
enhancement
ready
- Dominant language
- C++
- Stars
- 45
- Forks
- 57
- Avg merge
- 9h 19m
- Merged PRs (30d)
- 2
Description
This is tracking the parts of test_security not implemented in #230
#230 tests authentication and encryption in various scenarios but doesnt test access control.
Tests for access control should:
- have a yaml file (same format as the sros2 example) defining all the access control policies used by the tests
- use the
ros2 securitytool to generate keys, certificates, governance and permission files for these tests - test successful communication between nodes respecting the predefined access control policies
- test access denial for nodes violating the permissions defined in the yaml policies files
Contributor 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.
Research direction
Start by reading the existing test_security coverage and the authentication and encryption work tracked in #230. Use the linked sros2 sample_policy.yaml as the policy-format reference and inspect how the ros2 security tool is used to generate test credentials and policy files. Done means tests cover both permitted node communication and denial for nodes violating the YAML access-control policies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- authorization, security, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100