Backport of Compare public keys on trusted leaf certs, to prevent use of alternate certs with the same/forged serial numbers into release/1.14.x #25654
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
requested a review
from a team
as a code owner
hc-github-team-secure-vault-core
force-pushed
the
backport/sgm/vault-24406/certauth-check-nonca-pubkeys/incredibly-classic-impala
branch
from
2bec1a0
to
48af897
Compare
github-actions
bot
added
the
hashicorp-contributed-pr
sgmiller
approved these changes
Feb 26, 2024
|
Build Results: |
|
CI Results: |
sgmiller
deleted the
backport/sgm/vault-24406/certauth-check-nonca-pubkeys/incredibly-classic-impala
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 #25649 to be assessed for backporting due to the inclusion of the label backport/1.14.x.
The below text is copied from the body of the original PR.
By comparing public keys, we ensure the caller possessed the corresponding
private key of the role configured cert. The TLS stack will have validated
the signature of the provided certificate.
Overview of commits