opencontainers / opencontainers/runc
seccomp specification has non-obvious semantics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Right now, our seccomp rule specifications have this strange behaviour where if two arguments touch the same argument index, the argument list is treated as a series of OR conditions rather than AND conditions. This was added by e9193ba6e612c13c064449ee4189b268d1a9c94c to fix a breaking change, but the net result is that our seccomp rule generation feels at least slightly unpredictable as a result.
We should really rework this alongside the longer-term fix for #2151.
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 seccomp rule specification and generation code, then review commit e9193ba6e612c13c064449ee4189b268d1a9c94c and the longer-term fix described in issue #2151. The work is complete when overlapping argument conditions have deliberate, documented semantics and the resulting rule generation is predictable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100