letsencrypt / letsencrypt/boulder
Support ECH during http-01 and tls-alpn-01 validation
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
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.
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 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.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100