fips self tests have some potential for optimisation
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 30.8k
- Forks
- 11.5k
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
There are algorithms which are being used multiple times during the CASTs (e.g. SHA256).
There is some potential to reduce the testing load by replacing the second and later uses with other algorithms that are being independently self tested (e.g. SHA512 and SHA3-256 have their own self tests which could be rolled into the KDF/MAC tests easily enough.
This is unlikely to produce a large performance improvement but it will help a little.
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 CAST self-test implementations and identifying repeated SHA256 uses. Compare those uses with the independently self-tested SHA512 and SHA3-256 paths; the work is done when redundant algorithm testing is reduced without removing independent coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100