Originally created by @jcharaoui on GitHub (Oct 30, 2020).
As per a recent Let's Encrypt announcement, in a few weeks there will be a certificate transition that should result in a change from the current default fullchain of leaf+x3 to leaf+e1+x2-signed-by-x1. I'm wondering if dehydrated will handle that switch gracefully? Thanks.
Originally created by @jcharaoui on GitHub (Oct 30, 2020).
As per a recent Let's Encrypt [announcement](https://letsencrypt.org/2020/09/17/new-root-and-intermediates.html), in a few weeks there will be a certificate [transition](https://community.letsencrypt.org/t/detailed-2020-hierarchy/131019/3) that should result in a change from the current default fullchain of `leaf+x3` to `leaf+e1+x2-signed-by-x1`. I'm wondering if dehydrated will handle that switch gracefully? Thanks.
Dehydrated gets the certificate chain from the CA for each order, so this change will probably not have any impact and it will simply use the new chain.
@lukas2511 commented on GitHub (Nov 2, 2020):
Dehydrated gets the certificate chain from the CA for each order, so this change will probably not have any impact and it will simply use the new chain.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jcharaoui on GitHub (Oct 30, 2020).
As per a recent Let's Encrypt announcement, in a few weeks there will be a certificate transition that should result in a change from the current default fullchain of
leaf+x3toleaf+e1+x2-signed-by-x1. I'm wondering if dehydrated will handle that switch gracefully? Thanks.@lukas2511 commented on GitHub (Nov 2, 2020):
Dehydrated gets the certificate chain from the CA for each order, so this change will probably not have any impact and it will simply use the new chain.