From 697c14c75a28b4e76e381527de90a24814baf46c Mon Sep 17 00:00:00 2001 From: Luca Toscano Date: Sun, 7 Jan 2018 14:35:25 +0000 Subject: [PATCH] mod_md.xml: update MDCertificateAgreement's links Patch from Bernard Spil (brnrd freebsd.org). PR 61923 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1820464 13f79535-47bb-0310-9956-ffa450edef68 --- 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 9f17eb10e14..c995c2a4f72 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/2017.11.15-LE-SA-v1.2.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/2017.11.15-LE-SA-v1.2.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/2017.11.15-LE-SA-v1.2.pdf -- 2.47.3