Certificate chain: Use new-cert headers instead of fetching issuer url from the certificate #295

Closed
opened 2025-12-29 01:21:24 +01:00 by adam · 1 comment
Owner

Originally created by @lukas2511 on GitHub (Mar 11, 2018).

As @cpu mentioned in https://github.com/lukas2511/dehydrated/issues/493#issuecomment-371925404 ACMEv1 has a path to the issuer certificate in the headers of the new-cert reply. This should be a more reliable way to get the issuer certificate.

Originally created by @lukas2511 on GitHub (Mar 11, 2018). As @cpu mentioned in https://github.com/lukas2511/dehydrated/issues/493#issuecomment-371925404 ACMEv1 has a path to the issuer certificate in the headers of the new-cert reply. This should be a more reliable way to get the issuer certificate.
adam closed this issue 2025-12-29 01:21:25 +01:00
Author
Owner

@lukas2511 commented on GitHub (Apr 8, 2018):

No longer relevant as ACMEv2 delivers the full chain and chain-walking is no longer necessary.

@lukas2511 commented on GitHub (Apr 8, 2018): No longer relevant as ACMEv2 delivers the full chain and chain-walking is no longer necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/dehydrated#295