Repository navigation
Conversation
A validated authenticator proves only possession of the private key. Use SHOULD rather than MUST because RFC 9110 Section 4.3.4 allows specially configured clients and the issue notes divergence can be deliberate. Fixes httpwg#3576.
This branch has not been deployed
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
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.
Closes #3576.
Adds a section in security considerations suggesting that secondary certs should be validated with the same scrutiny as a certificate presented in the initial TLS handshake. The text says SHOULD as it may be deliberate to not always do this, but the vast majority of clients should.