| commit | 44099d59250dd41e3fc00e16b21e2af14b339521 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Feb 20 13:41:50 2020 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Mar 02 18:29:59 2020 +0000 |
| tree | 62c7aba4658201969350c687d6295cdc911d24b7 | |
| parent | 3280287c0609b7aefd5c84405b3f6ef4683a8f80 [diff] |
Tidy up transitions out of 0-RTT keys on the client. This change does two things. First, it funnels the transition out of 0-RTT into one function so that, later, when QUIC releases keys in set_(read|write)_state, we can handle the QUIC quirks better. Second, it switches to handshake (or initial) keys as soon as 0-RTT is closed. In particular, if EncryptedExtensions reports a 0-RTT reject, we switch keys before processing Certificate. This way, if we then reject the server certificate, we send the alert with keys the server can read. If there is an error in EncryptedExtensions or earlier, we do not know whether the server is expecting 0-RTT-encrypted alerts or handshake-encrypted alerts, so we cannot reliably send an alert. This is fine because all such error cases are server implementation bugs and alerts are purely a debugging courtesy. However, after a 0-RTT reject, we may reject the Certificate message due to local policy, in which case the certificate error alerts make more sense. Bug: 303 Change-Id: I4c4bc9c8ab2c2ecb89e20141518e1b7ea7b39af3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40125 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
Project links:
There are other files in this directory which might be helpful: