Originally created by @bjacke on GitHub (Dec 4, 2020).
This requirest is related to issue #785 but it's not the same.
If OCSP_MUST_STAPLE is enabled and if the initial ocsp fetch (after a a fresh new cert was issued) was not successful, then dehydrated should continue trying to fetch a valid and matching ocsp response. I saw recently that it took 30min till the ocsp server had the ocsp status for a new cert. Only if the initial ocsp fetching could be done successfully, the cert deployment should continue.
Originally created by @bjacke on GitHub (Dec 4, 2020).
This requirest is related to issue #785 but it's not the same.
If OCSP_MUST_STAPLE is enabled and if the initial ocsp fetch (after a a fresh new cert was issued) was not successful, then dehydrated should continue trying to fetch a valid and matching ocsp response. I saw recently that it took 30min till the ocsp server had the ocsp status for a new cert. Only if the initial ocsp fetching could be done successfully, the cert deployment should continue.
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 @bjacke on GitHub (Dec 4, 2020).
This requirest is related to issue #785 but it's not the same.
If OCSP_MUST_STAPLE is enabled and if the initial ocsp fetch (after a a fresh new cert was issued) was not successful, then dehydrated should continue trying to fetch a valid and matching ocsp response. I saw recently that it took 30min till the ocsp server had the ocsp status for a new cert. Only if the initial ocsp fetching could be done successfully, the cert deployment should continue.