ocb3: use parallel-capable APIs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 961
- Forks
- 200
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 6
Description
Right now, ocb3 exclusively uses BlockCipherEncrypt::encrypt_block and BlockCipherDecrypt::decrypt_block. Although VAES support is coming in block-ciphers#491, ocb3 won't be able to take advantage of its (2-5x) speedups until encrypt_blocks*/decrypt_blocks* APIs are used.
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 locating ocb3's uses of BlockCipherEncrypt::encrypt_block and BlockCipherDecrypt::decrypt_block, then read the parallel encrypt_blocks*/decrypt_blocks* APIs introduced for block-ciphers#491. The work is done when ocb3 uses the parallel-capable APIs where applicable and its existing behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100