openmcp-project / openmcp-project/backlog
User Story: Resolving FIPS incompliance in gardener/landscaper caused by internal code
Open
Nobody has claimed this yet.
area/open-control-plane
kind/user-story
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Description
Required FIPS changes: See sub-issues below.
@robertgraeff & @Diaphteiros : We need a bit of investigation in each of these issues reg complexity and whether a potential fix could be risky for stakeholders.
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 locating the sub-issues referenced in the description and reviewing their requested FIPS changes. The payload names no files, tests, or entry points, so use those sub-issues to identify the affected gardener/landscaper code and the stakeholder risks. Done means the required investigation and any agreed FIPS fixes are documented or completed.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100