forked from google/boringssl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Check the second ClientHello's PSK binder on resumption.
We perform all our negotiation based on the first ClientHello (for consistency with what |select_certificate_cb| observed), which is in the transcript, so we can ignore most of the second one. However, we ought to check the second PSK binder. That covers the client key share, which we do consume. In particular, we'll want to check if it we ever send half-RTT data on these connections (we do not currently do this). It is also a tricky computation, so we enforce the peer handled it correctly. Tested that both Chrome and Firefox continue to interop with this check, when configuring uncommon curve preferences that trigger HRR. (Normally neither browser sees HRRs against BoringSSL servers.) Update-Note: This does enforce some client behavior that we hadn't been enforcing previously. However, it only figures into TLS 1.3 (not many implementations yet), and only clients which hit HelloRetryRequest (rare), so this should be low risk. Change-Id: I42126585ec0685d009542094192e674cbd22520d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37124 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Steven Valdez <svaldez@google.com>
- Loading branch information
Showing
11 changed files
with
264 additions
and
151 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.