letsencrypt / letsencrypt/pebble
Please support generating the end-entity certificate
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 787
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
For simplicity of setup, please consider generating the end-entity certificate and private key for the challenge server itself. That would allow running pebble without having to check those files into the repository that's trying to run pebble in CI. The management interface could serve the appropriate CA public key (also generated).
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
The issue names no files, tests, or entry points. Start by locating Pebble's certificate-authority setup and management interface, then determine how the challenge server's end-entity certificate, private key, and CA public key should be generated and exposed. Done means CI can run Pebble without checked-in certificate files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100