Markus Germeier 76a37834be fixed logic to check status from our challenge
the old code had a problem and would interpret a challenge that
returned "pending" and then "invalid" as valid.

This code actually has another problem. The RFC defines:

"status (optional, string):  The status of this authorization.
 Possible values are: "pending", "valid", and "invalid".  If this
 field is missing, then the default value is "pending"."

So actually the correct way to implement this would be:

while [[ -z "${status}" ]] || [[ "${status}" = "pending" ]]; do

But without further checks this might lead to an endless loop. So this
is "good enough(tm)". ;)
2015-12-06 15:51:38 +01:00
2015-12-05 02:31:06 +01:00
2015-12-05 02:31:06 +01:00
2015-12-05 02:31:06 +01:00
2015-12-05 02:31:06 +01:00

letsencrypt.sh

letsencrypt client implemented as a shell-script

Description
No description provided
Readme MIT 3.1 MiB
Latest
2025-05-18 01:34:32 +02:00
Languages
Shell 100%