letsencrypt / letsencrypt/pebble
Check CAA records
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
It looks like although challtestrv supports setting a CAA record, pebble does not check those records, and does not issue an error if CAA policy do not allow letsencrypt.org to issue certificates.
It would be nice to test this type of error.
Contributor guide
No contributing guide indexed for this repository
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 Pebble's certificate issuance validation for CAA records and compare it with challtestrv's existing CAA behavior. Identify the relevant issuance tests and add coverage for a CAA policy that does not allow letsencrypt.org to issue certificates, with the expected error confirming the policy is enforced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100