letsencrypt / letsencrypt/pebble

alternate chains should be enabled by default

Open
#317 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
787
Forks
176
PR merge metrics
No merged PRs in 30d

Description

The current behavior of Boulder and Letsencrypt is to offer alternate chain support. I believe this should therefore be the default behavior of this project.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating Pebble's alternate-chain handling and the configuration or entry point that determines its default behavior. Confirm how Boulder and Let's Encrypt offer alternate chains, then verify that a fresh Pebble setup enables the behavior by default without requiring an explicit option.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.