From c8333f5a5699295568d0208db224cfcc1cae3b2e Mon Sep 17 00:00:00 2001
From: Rogdham <contact@rogdham.net>
Date: Mon, 30 Mar 2020 21:26:00 +0200
Subject: [PATCH] Fix challenge response POST body in ACMEv2

Per https://tools.ietf.org/html/rfc8555#section-7.5.1

> The client indicates to the server that it is ready for the challenge
> validation by sending an empty JSON body ("{}") carried in a POST
> request to the challenge URL (not the authorization URL).
---
 dehydrated | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dehydrated b/dehydrated
index aacb66b..1362f8a 100755
--- a/dehydrated
+++ b/dehydrated
@@ -809,7 +809,7 @@ sign_csr() {
     if [[ ${API} -eq 1 ]]; then
       result="$(signed_request "${challenge_uris[${idx}]}" '{"resource": "challenge", "keyAuthorization": "'"${keyauths[${idx}]}"'"}' | clean_json)"
     else
-      result="$(signed_request "${challenge_uris[${idx}]}" '{"keyAuthorization": "'"${keyauths[${idx}]}"'"}' | clean_json)"
+      result="$(signed_request "${challenge_uris[${idx}]}" '{}' | clean_json)"
     fi
 
     reqstatus="$(printf '%s\n' "${result}" | get_json_string_value status)"
-- 
2.47.2