RustCrypto / RustCrypto/block-ciphers
aes: introduce optional software backend based on lookup tables?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 784
- Forks
- 157
- Avg merge
- 15h 24m
- Merged PRs (30d)
- 9
Description
In some use cases timing variability is not a concern and IIUC table-based implementations are faster than fixslising. We could introduce such implementation gated behind an aes_backend_soft="some_scary_hazmat_value" flag.
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 the AES implementation and the existing backend-selection entry points; the issue names no files or tests. Determine how an optional lookup-table backend and the aes_backend_soft="some_scary_hazmat_value" flag should fit the project, then define completion around selecting that backend only when explicitly enabled and covering its behavior with tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100