From: Stefan Eissing
Date: Tue, 20 Feb 2018 13:00:39 +0000 (+0000)
Subject: On the 2.4.x branch:
X-Git-Tag: 2.4.31~34
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=90969b7afc5de0a663d79a297f6aa3c784871872;p=apache
On the 2.4.x branch:
Merged r1820464 from trunk.
elukey: mod_md update to current certifcate agreement URL.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1824871 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/docs/manual/mod/mod_md.xml b/docs/manual/mod/mod_md.xml
index 2d217d0c1d..c1759dea4a 100644
--- a/docs/manual/mod/mod_md.xml
+++ b/docs/manual/mod/mod_md.xml
@@ -133,7 +133,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/2017.11.15-LE-SA-v1.2.pdf
MDomain example.org www.example.org
<VirtualHost *:443>
@@ -233,11 +233,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/2017.11.15-LE-SA-v1.2.pdf
MDomain example.org www.example.org mail.example.org
@@ -264,7 +264,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/2017.11.15-LE-SA-v1.2.pdf