TLS 1.3 PHA with OCSP Stapling#10421
Open
kojo1 wants to merge 1 commit intowolfSSL:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
CertificateRequest is missing the
status_requestextension.When the server triggers PHA via
wolfSSL_request_certificate(),the
status_requestextension is suppressed, so the server cannotask the client to staple OCSP information for its certificate
(RFC 8446 §4.2 / §4.4.2.1).
The PHA-side client Certificate is not subject to the
server's OCSP-status check.
ProcessPeerCerts()only entered theOCSP path for
WOLFSSL_CLIENT_END, so the OCSP staple supplied bythe client was never validated.
Fixes zd#21555
Testing
added test_tls13_pha_status_request
Checklist