Support ECH during http-01 and tls-alpn-01 validation

Open
#9,009 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
networking, security

Research direction

Start by tracing bdns DNS lookups and the TLS-ALPN-01 validation path, including HTTP-01 requests that follow an HTTP-to-HTTPS redirect. Check where the validation tls.Config is built and where feature flags are defined. Done means HTTPS records can be queried, ECHConfigList data reaches the configured validation connection, and the behavior is gated by a feature flag.

Written by the indexing model from the issue text.

Description

In order to add ECH support during validation, we need to:

  • add the ability for bdns to lookup HTTPS records
  • do an HTTPS lookup before making TLS connections during validation (i.e. all TLS-ALPN-01 conns, and HTTP-01 conns that are the result of an http->https redirect)
  • copy the serialized ECHConfigList from the HTTPS record into the tls.Config we use to make the request

It may be best/simplest to only do this during tls-alpn-01 at first, to prove it out. Also, it should all be behind a feature flag, of course.

Dominant language
Go
Stars
5.8k
Forks
649
Avg merge
3d 23h
Merged PRs (30d)
24

Contributor guide

Open the contributing guide

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 letsencrypt/boulder

All issues in letsencrypt/boulder

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.