rustls_{server/client}_config_builder_new_custom() parameters
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 43
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 10
Description
As I see it, the new rustls_client_config_builder_new_custom and rustls_server_config_builder_new_custom require specification of protocols and ciphersuites and panic if one is NULL.
Questions:
- how can one configure a supported cipher without mentioning the tls protocol version?
- how can one enable a certain minimum protocol version without know all available?
- how can one enable a specific protocol version without being aware which ciphers belong to it?
- what is the outcome of a cipher and tls version that do not match?
Thanks for your help.
Contributor guide
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 examining rustls_client_config_builder_new_custom and rustls_server_config_builder_new_custom, focusing on their protocol and ciphersuite parameters and NULL handling. Determine the expected behavior for omitted, minimum, or mismatched protocol and cipher selections; the issue is done when that behavior is clearly documented or the API design is revised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100