| commit | 1c337e566d98a46798fe76c170c35e8c1a3ca6ea | [log] [tgz] |
|---|---|---|
| author | Jesse Selover <jselover@google.com> | Fri Aug 10 13:28:47 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Aug 10 20:06:22 2018 +0000 |
| tree | 910025ec6ed36d97aa00b07b4b71a426503ecd3e | |
| parent | bdc409801f793bc15cae6e57697e061b96dd9487 [diff] |
Option to reverify certs on resumption. Works in the 1.3 and 1.2 client handshakes, not implemented on the server for now. Creates an SSL_CTX option to reverify the server certificate on session resumption. Reverification only runs the client's certificate verify callback. Adds new states to the client handshakes: state_reverify_server_certificate in TLS 1.2, and state_server_certificate_reverify in TLS 1.3. Adds a negative test to make sure that by default we don't verify the certificate on resumption, and positive tests that make sure we do when the new option is set. Change-Id: I3a47ff3eacb3099df4db4c5bc57f7c801ceea8f1 Bug: chromium:347402 Reviewed-on: https://boringssl-review.googlesource.com/29984 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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.
There are other files in this directory which might be helpful: