Backport of Fix issuer patch of leaf_not_after_behavior into release/1.13.x #20344
Conversation
This file contains 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
hc-github-team-secure-vault-core
force-pushed
the
backport/cipherboy-fix-patch-leaf-not-after/frequently-fit-seahorse
branch
from
4d8b6c8
to
cc6b6bd
Compare
hc-github-team-secure-vault-core
force-pushed
the
backport/cipherboy-fix-patch-leaf-not-after/frequently-fit-seahorse
branch
from
f0cd7cc
to
ba4237d
Compare
cipherboy
approved these changes
Apr 25, 2023
…not-after/frequently-fit-seahorse
cipherboy
deleted the
backport/cipherboy-fix-patch-leaf-not-after/frequently-fit-seahorse
branch
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.
Backport
This PR is auto-generated from #20341 to be assessed for backporting due to the inclusion of the label backport/1.13.x.
The below text is copied from the body of the original PR.
This variable had a spelling mistake in the handler;
GetOk(...)appears to swallow scheme failures, unlike the regularGet(...)which panics.Overview of commits