Consider supporting CAESAR recommendations
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
The CAESAR competition for standardizing new AEAD algorithms wrapped up a while ago and some new very fast constructions were recommended (see, https://competitions.cr.yp.to/caesar-submissions.html). For benchmarks, see eBACS.
Most of these recommendations (especially the recommendations for use case 2) take advantage of AES-NI instructions already widely available in hardware. There's also no more patents on AES-OCB iirc.
Is there any interest in bringing these algorithms to the browser?
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 with the CAESAR submissions and eBACS benchmark links in the issue, then review the Web Cryptography API scope. The issue does not name files, tests, or a specific algorithm set; completion would require an agreed set of browser-supported constructions and a defined API change.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, cryptography, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100