From 122405df8eda0bae3595dc9b42fca00364196e11 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 31 Aug 2026 21:42:13 +0200 Subject: [PATCH] 020: the server version is not it either MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pinned 2.5.0 rather than latest, on the suspicion that its draft profiles extension was involved. Identical failure, so that is ruled out and recorded — two of the three guesses in this issue have now been tested and both were wrong, which is the useful half. The scenario keeps the pin regardless; it should have had one from the start. --- .../00-report.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/04-ISSUES/020-a-certificate-is-issued-and-never-collected/00-report.md b/04-ISSUES/020-a-certificate-is-issued-and-never-collected/00-report.md index 34e51fb..98c3fd8 100644 --- a/04-ISSUES/020-a-certificate-is-issued-and-never-collected/00-report.md +++ b/04-ISSUES/020-a-certificate-is-issued-and-never-collected/00-report.md @@ -58,15 +58,16 @@ may say nothing about behaviour against a public authority. | a hand-written server config | suspected, and wrong. Replacing it with the server's **own** default config, changing only the challenge port, gives the identical error | | the finalize URL being empty | the authority logs finalisation being accepted | | the challenge path | the authorisation goes valid | +| the server version | pinned 2.5.0 behaves exactly as `latest`, so the draft profiles extension is not it | ## Where it might be - **The order's `certificate` field is absent when the client reads it.** The client waits for the order to become valid and only then fetches, so an empty location on a valid order is the remaining shape. -- **A moving tag was used.** `pebble:latest` advertises a draft *profiles* extension in its - directory. A pinned older version is being tried — the third time today that not pinning a tag - cost a run. +- ~~**A moving tag was used.**~~ **Ruled out.** `pebble:latest` advertises a draft *profiles* + extension, so a pinned 2.5.0 was tried: **identical failure**. The scenario now pins it anyway, + which it should have from the start. ## Why this is filed rather than pursued