Publish a rustls-platform-provider crate
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.6k
- Forks
- 896
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 39
Description
The default crypto provider for Rustls (starting from version 0.23) is aws-lc-rs and it make sense.
However for windows platforms, symcrypt should be used as the default crypto provider. This choice aligns with Windows-native cryptographic primitives and leverages deep Azure and Microsoft ecosystem integration. Using symcrypt also enables reuse of the existing internal crypto stack, reduces duplication, and ensures better compatibility with platform security features, updates, and validation processes.
I understand that it can be selected through features, but I guess default selection should be one best for platform and then if someone wants can choose not to use default based on scenario specific requirement.
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 reviewing Rustls's existing feature-based crypto-provider selection and the requirements implied by the proposed rustls-platform-provider crate. Define the crate boundary and Windows default behavior, while preserving an option for scenario-specific providers; done means the crate is published and the platform-specific selection works as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography, operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100