Support verifying/accessing SCTs inside certificates

Open
  • Is something wrong?
#105 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
security

Research direction

Start by reviewing EndEntityCert and the certificate-validation flow, then compare the two options described: adding an sct.rs dependency and accepting sct::Log values, or exposing SCTs for callers to verify externally. Done requires a decided API that supports accessing or verifying SCTs inside certificates; the issue does not name files or tests.

Written by the indexing model from the issue text.

Description

If we supported SCTs here we could enable people wanting to do CT verification of the certificates they see.

We could either do this directly by taking a dependency on sct.rs and requiring certificate validation to take a set of sct::Logs. It's more integrated but less flexible.

Alternatively we could let callers access the SCTs given a EndEntityCert and do the verification themselves outside this crate, after they've done other checks.

Dominant language
Rust
Stars
167
Forks
112
Avg merge
4h 28m
Merged PRs (30d)
4

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/webpki

All issues in rustls/webpki

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.