RFE: Stable C API and ABI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 160
- Forks
- 102
- Avg merge
- 28m
- Merged PRs (30d)
- 5
Description
Many applications and libraries that do certificate validation are not written in Rust. Providing a C API would not only allow them to use a memory-safe validation implementation, but (once #403 is implemented) it would give them the same features that platform APIs do on Windows, Darwin, and Android.
For various reasons, to be useful this would need to have a stable API and ABI.
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
No files, tests, or entry points are named. Start by reading #403 and reviewing the certificate-validation scope and the platform APIs referenced in the issue. Done means a specified stable C API and ABI that exposes the required validation features, with the scope agreed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- api, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100