From fc4fae45811dd87a8e34e31ca2a06fc0b5cc6909 Mon Sep 17 00:00:00 2001 From: Guilhem Moulin Date: Fri, 28 Apr 2023 10:06:27 +0200 Subject: =?UTF-8?q?client:=20Handle=20"ready"=20=E2=86=92=20"processing"?= =?UTF-8?q?=20=E2=86=92=20"valid"=20status=20change=20during=20newOrder.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Instead of just "ready" → "valid", which may be what we observe when the server is fast enough, but according to RFC 8555 sec. 7.1.6 the state actually transitions via "processing" state and we need to account for that. It appears Let's Encrypt staging environment now has different timing conditions and lacme is unable to request certificates due to this issue. Cherry-picked from 53238c70f7a12e233a6ca83cf2b50168e5b9592e. Closes: #1034834 --- debian/patches/series | 1 + 1 file changed, 1 insertion(+) (limited to 'debian/patches/series') diff --git a/debian/patches/series b/debian/patches/series index 1c2191a..70709e0 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -1 +1,2 @@ Mention-the-Debian-BTS-in-the-manpages.patch +client-Handle-ready-processing-valid-status-change-during.patch -- cgit v1.2.3