microsoft/msquic

Using custom CA with TLS certificates

Open

#2,820 opened on Jun 14, 2022

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C (671 forks)github user discovery
Area: APITLS: SchannelTLS: quicTLSexternalfeature requestgood first issuehelp wanted

Repository metrics

Stars
 (4,712 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the feature you'd like supported

Right now TLS certificate verification uses only system CA store. But in some cases custom CA certificates may be prefered (for example, non-HTTP/3 QUIC usage). For this we need to specify custom CA path(es), which should be passed to TLS backend. But MsQuic doesn't support that at this moment.

Proposed solution

Add function or struct field that will pass custom CA path(es) to TLS backend (for example, SSL_CTX_load_verify_locations for OpenSSL).

Additional context

No response

Contributor guide

Research direction
Investigate how MsQuic uses the TLS backend (e.g., OpenSSL) and where certificate verification happens. Propose a way to add custom CA paths via SSL CTX load verify locations.
Tech stack
c
Domain
networkingsecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
CTLS/SSL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35