Update QUIC client fuzzer to test 0-RTT
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- c
- Domain
- testing-qa
Research direction
Start with fuzz/quic-client.c and inspect main to understand how existing cases are exercised. Add SSL_write_early_data as a 0-RTT case, then run the QUIC client fuzzer and confirm that the new path is covered without errors.
Written by the indexing model from the issue text.
Description
Update fuzz/quic-client.c to also test SSL_write_early_data as one of the cases in main
- Dominant language
- No language data
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from openssl/project
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
OTC
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100