Make systemcrypto backends to be compiled and distributed as lib/fips140/systemcrypto.zip
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
In cases where it is interesting to only use fips algorithms from the systemcrypto backend, it would be interesting to support packaging for example openssl backend as as lib/fips140/systemcrypto.zip which would then slot into existing toolchain builds as is.
Note, this likely will restrict the number of available features, and might not be at all possible - as the rest of the golang toolchain has workaround specific to the geomys.zip snapshots.
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 investigating how the Go toolchain handles geomys.zip snapshots and how the systemcrypto backend is currently built. Determine whether an OpenSSL-backed systemcrypto.zip can be placed at lib/fips140/systemcrypto.zip without losing required features. Done means establishing whether this packaging approach is feasible and documenting its supported limitations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100