Detect when there are new crypto files to patch
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
Most of import "crypto/internal/fips140/... imports that are not within "crypto/internal/fips140" requires patching on our side to redirect those usages to our crypto backends. We currently detect new things to patch by having @qmuntal manually inspecting all the commits that land into crypto, and that's not scalable.
We should have a tool that checks in CI that we haven't missed anything.
Design pending.
Contributor guide
No contributing guide indexed for this repository
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 examining imports under crypto/internal/fips140 and the existing CI configuration to understand how crypto changes are currently checked. Define the tool's scope and integration so CI detects new imports outside crypto/internal/fips140 that require patching; done means missed crypto files are reported automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100