Handshake with different settings
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
The handshake test on master is slower because it started to offer and use X25519MLKEM768. We should consider to have handshake tests with specific settings, so that we can compare:
- different branches
- different algorithm combinations
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 with the handshake test on master and identify how its current settings are selected. Define how tests can specify individual settings and algorithm combinations, then verify that results can be compared across branches and configurations. The payload does not name a source file or test command, so locate those from the handshake test entry point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cryptography, performance, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100