From a8f478fb3d2fd38709b6c6ca4c1f378d890d2df1 Mon Sep 17 00:00:00 2001 From: Daniel McCarney Date: Wed, 22 Jan 2025 18:09:48 -0500 Subject: [PATCH] docs: rm mention of subproblems being unimpl'd MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Support for RFC 8555 subproblems (ยง 6.7.1) was implemented in Pebble v2.5.0: https://github.com/letsencrypt/pebble/releases/tag/v2.5.0 --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5a384414..cf243ae5 100644 --- a/README.md +++ b/README.md @@ -55,9 +55,8 @@ clients are not hardcoding URLs.) ## Limitations Pebble is missing some ACME features (PRs are welcome!). It does not presently -support subproblems, or pre-authorization. Pebble does not support revoking a -certificate issued by a different ACME account by proving authorization of all -of the certificate's domains. +support pre-authorization or revoking a certificate issued by a different ACME +account by proving authorization of all of the certificate's domains. Pebble does not perform all of the same input validation as Boulder. Some domain names that would be rejected by Boulder/Let's Encrypt may work with Pebble.