From 42344a9fb2893f3cfe82d766c27fbe88f68256bd Mon Sep 17 00:00:00 2001
From: Stefan Eissing
Second, mod_md offers an alternate OCSP Stapling implementation. This works with @@ -495,7 +495,7 @@ MDomain example2.org auto For testing, CAs commonly offer a second service URL. The 'test' service does not give certificates valid in a browser, but are more relaxed in regard to rate limits. - This allows for verfication of your own setup before switching + This allows for verification of your own setup before switching to the production service URL.
You can configure those globally or for a specific MDomain. Since these values allow anyone to register under the same account, it is - adivsable to give the configuration file restricted permissions, + advisable to give the configuration file restricted permissions, e.g. root only.
@@ -1512,4 +1512,86 @@ MDMessageCmd /etc/apache/md-message
+ The time between certificate checks. By default, the validity + and need for renewals is checked twice a day. This interval is + not followed precisely. Instead the module randomly applies + a +/-50% jitter to it. With the default of 12 hours, this + means the actual time between runs varies between 6 and 18 + hours, jittered anew every run. This helps to mitigate + traffic peaks at ACME servers. +
+ The minimum duration you may configure is 1 second. It is + not recommended to use such short times in production. +
++ This about a non-standard ACME extension by Let's Encrypt. +
+ Lets Encrypt announced they will add Certificate Profiles + support in their CA during 2025, beginning with their staging + servers. This, among some other details, let's you select the + lifetime of the certificates you get. The "default" profile + will keep the 90 days and a "tlsserver" profile will issue + certificates with only 6 days of validity. +
+ If you do not change your mod_md configuration, you will + continue to get the 90 days certificates. Should you believe + that a shorter lifetime is beneficial for you (and take the + risk that the renewal time is way shorter), + you can configure the profile to use via 'MDProfile tlsserver'. +
+ The profile names are defined by the CA. If a profile you + configure is not available, no profile will be used and + the certificate will be issue according to what the CA + considers default. +
+ See
+ Controls if a
+ When not mandatory and a profile is not offered by the CA, + renewals will be performed without specifying a profile and + the CA will issue a certificates according to its defaults. +
+