No way to chain policy operations after some are executed
Open
Nobody has claimed this yet.
bug
CRIT-4
- Dominant language
- C
- Stars
- 14
- Forks
- 9
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 33
Description
When the outcome of a security operation influences policy behavior, there is currently no way for a policy provider to indicate during finalize "query and process this bundle again" with follow-on security operations.
If implemented, the BSL would need a limit counter to disallow a bad PP to recycle endlessly.
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 tracing the policy provider finalize path and how the bundle is queried and processed with follow-on security operations. Define how a provider requests another processing pass and how the limit counter bounds recycling. Done means the behavior is implemented with protection against endless reprocessing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100