RustCrypto / RustCrypto/formats
Simd backends for encoders/decoders
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 338
- Forks
- 188
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 15
Description
Wanted to know if you'd be interested / accepted a CT SIMD implementations for some of the formats here, I've been playing with the idea of adapting SIMD encoders/decoders to be data independent, as a lot of times the main parts already are, I currently looked at hex and base64.
For example I've wrote this hex repo where I also verified CT with valgrind, and safety with miri, And I'm working on a ctutils API: https://github.com/elichai/better-hex (*)
But contributing the backends to the RustCrypto crates would be more meaningful IMHO.
(*) yes, commits and some parts of the code were written by LLMs but I'm fully involved and reviewed the LLMs portions
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 reviewing the issue's proposed scope for constant-time SIMD implementations, especially the hex and base64 formats, and the linked better-hex repository. Before coding, clarify which RustCrypto crates and interfaces would accept these backends; done should mean an agreed format scope with constant-time and safety validation comparable to the stated Valgrind and Miri checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100