From bb2f6105edd8bc5c61698de2f6080f9d765516a0 Mon Sep 17 00:00:00 2001
From: Bernard Spil
Date: Wed, 20 Dec 2017 15:02:39 +0100
Subject: [PATCH] Update LetsEncrypt Agreement URL
---
docs/manual/mod/mod_md.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/manual/mod/mod_md.xml b/docs/manual/mod/mod_md.xml
index e06d0d21bf2..12e489c9ac2 100644
--- a/docs/manual/mod/mod_md.xml
+++ b/docs/manual/mod/mod_md.xml
@@ -109,7 +109,7 @@ MDomain example.org
Example
ServerAdmin mailto:admin@example.org
-MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf
+MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
MDomain example.org www.example.org
<VirtualHost *:443>
@@ -209,11 +209,11 @@ MDomain example2.org auto
so that you understand what they offer and what they might exclude or require from you.
mod_md cannot, by itself, agree to such a thing.
- In case of Let's Encrypt, their current Terms of Service are here.
+
In case of Let's Encrypt, their current Terms of Service are here.
Those terms might (and probably will) change over time. So, the certificate renewal might require you to update this agreement URL.
Example
-MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf
+MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
MDomain example.org www.example.org mail.example.org
@@ -240,7 +240,7 @@ MDomain example.org www.example.org mail.example.org
LE Staging Setup
MDCertificateAuthority https://acme-staging.api.letsencrypt.org/directory
-MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.1.1-August-1-2016.pdf
+MDCertificateAgreement https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf