Improvements to client certificate support

Open
  • Is something wrong?
#1,164 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
authentication, cryptography, security

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.

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
Dominant language
Rust
Stars
7.7k
Forks
947
Avg merge
3d 11h
Merged PRs (30d)
46

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/rustls

All issues in rustls/rustls

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.