Current secop member leaks sample policy implementation details
Open
Nobody has claimed this yet.
sustainment
- Dominant language
- C
- Stars
- 14
- Forks
- 9
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 33
Description
The member BSL_SecOper_s::policy_action is an enumeration specific to the sample PP for BSL. This leaks details that belong strictly within the policy provider.
Instead of having a specific member variable, the secop should contain opaque 'user data' supplied by the policy provider and accessed only by the provider.
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 BSL_SecOper_s::policy_action and every place the sample PP policy provider reads or writes it. Identify the secop and policy-provider entry points involved; done means the secop exposes only opaque provider-supplied user data and no longer depends on the sample PP's policy_action enumeration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100