letsencrypt / letsencrypt/boulder
Support `ca-tbr-` CAA validationmethods labels
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Per Section 4.2.2.1.2 of Version 2.2.8 of the BRs:
If a CA performs domain validation using a mechanism that can be represented by multiple labels (e.g. 'http-01' and 'ca-tbr-19'), the CA SHOULD accept any of the labels as granting permission to issue.
This is only a SHOULD, so we're under no obligation, but worth considering and formulating concrete reasoning if we choose not to do so.
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
No files or tests are named. Start by locating the CAA validation-method handling in the Boulder codebase and compare its behavior with Section 4.2.2.1.2 of the cited BRs; done means the project has a decided, tested behavior for accepting equivalent ca-tbr-* and existing validation labels, or a documented reason not to do so.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100