CA: Stop using OCSP status NotReady #8394
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsha
requested changes
Sep 11, 2025
jsha
approved these changes
Sep 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stop setting "OcspNotReady: true" when asking the SA to store a linting precertificate, and stop calling SetCertificateStatusReady after precertificate issuance has succeeded. Because these two calls are always made in sequence by the same CA instance, this change will not leave any database entries permanently hanging in the "NotReady" state (unless an error occurs between the two calls, as is the case today).
A follow-up change will remove the corresponding support on the SA side.
Part of #8343