Improvements to client certificate support
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.6k
- Forks
- 896
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 39
Description
Within webpki and prior to a client cert being accepted,
- CRL support
- Path validation, likely incorporating webpki CRL support
After a connection has been established,
- Provide pub api access to the [unparsed?] client certificate as well as issuer chain
- Provide pub api access to the parsed certificate entities/fields/extensions, including the Subject entity
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 locating the client-certificate handling and public API entry points, then review how webpki performs CRL and path validation. Done means exposing the client certificate and issuer chain, plus parsed certificate entities, fields, extensions, and the Subject entity through a defined public API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100