starred/certbot-certbot-2
1
0
Fork 0
mirror of https://github.com/certbot/certbot.git synced 2026-08-02 16:12:09 +02:00
Code Issues Packages Projects Releases Wiki Activity

renewal: use lineage-specific server for ARI (#10307)

Browse Source 
Previously, we were constructing an ACME client for ARI checking that
used the global value for `server`, not the one recorded in a lineage's
renewal file.

This resulted in errors in the logs and failure to observe ARI for
lineages that used a non-default `--server` (e.g. staging or non-Let's
Encrypt CAs).

---------

Co-authored-by: ohemorange <ebportnoy@gmail.com>
This commit is contained in:
Jacob Hoffman-Andrews
2025-06-09 11:44:04 -07:00
committed by GitHub
co-authored by ohemorange
parent a75057042f
commit 1d9fc8dccf
5 changed files with 34 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
certbot/CHANGELOG.md
+5 -1
View File
@@ -6,7 +6,11 @@ Certbot adheres to [Semantic Versioning](https://semver.org/).
### Added
*
* ACME Renewal Info (ARI) support. https://datatracker.ietf.org/doc/draft-ietf-acme-ari/
`certbot renew` will automatically check ARI when using an ACME server that supports it,
and may renew early based on the ARI information. For Let's Encrypt certificates this
will typically cause renewal at around 2/3rds of the certificate's lifetime, even if
the renew_before_expiry field of a lineage renewal config is set a later date.
### Changed