Closed mschiff closed 1 year ago
Dehydrated does some funky stuff for the deprecated acme v1 API, walking issuer uris etc and caching by issuer name, but for v2/rfc8555 operation it always retrieves a fresh and full chain from the CA, on every renewal.
From https://letsencrypt.org/2023/07/10/cross-sign-expiration.html:
I opened this issue so it can be verifed if dehydrated will still function properly after the expiration of the cross-sign on 2024-09-30
dehydrated is caching chains and I could not tell whether this will be a problem or not in the future by having a quick look at it...