RustCrypto / RustCrypto/rustls-rustcrypto
Tracking issue - Gathering Test Vectors
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 130
- Forks
- 21
- Avg merge
- 18h 6m
- Merged PRs (30d)
- 1
Description
I've done some initial plumbing for internal self-validation at
- #28
I have a static test generator I'm working on similar to wycheproof I did for curve25519-dalek:
Plumbing sources progress
- #31
- #30
- #49
- #52
- #54
Any other vectors we should plumb ? These are the tests we run internally w/o downstream deps / internet access e.g. pure TLS or with bare minimal application part if any so it can be used in CI
Also hunting vectors we can just simply plumb without creating new things - worst case they can be upstreamed as provider validation suite if something needs to be created fresh
See if we can use a transcript like this: https://tls13.xargs.org/
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 reading #28 and the progress issues #30, #49, #52, and #54, then review the linked curve25519-dalek generator and tls13.xargs.org transcript. Done means agreeing on the needed test vectors and documenting or plumbing them into CI without downstream dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100