letsencrypt / letsencrypt/boulder
Add CAA presence/validity information to ValidationRecords
Open
Nobody has claimed this yet.
area/va
kind/enhancement
starter
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
Since this is important information about an authorization.
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
The issue concerns adding CAA presence and validity information to ValidationRecords. Start by locating ValidationRecords and its consumers in the Boulder codebase, then determine the required record fields and behavior; done when the intended CAA information is defined and consistently available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100