| commit | 9b2cdb769ac420b0f98ff7ef5df61115bbddc3d8 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Apr 01 23:21:53 2021 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon May 10 18:20:35 2021 +0000 |
| tree | a034e34855418b8acd97e2230ff89c498963fcd7 | |
| parent | 9f55d972854d0b34dae39c7cd3679d6ada3dfd5b [diff] |
Add SSL_can_release_private_key. Callers using private key callbacks may retain non-trivial state with a private key. In many cases, the private key is no longer necessary immediately after the first round-trip (e.g. non-HRR TLS 1.3 connections). Add a function that callers can query to drop the state a hair earlier. This is tested in two ways. First, the asserts in front of using the key, combined with existing tests, ensure we don't start reporting it too early. Second, I've added tests in ssl_test.cc to assert we report it as early as we expect to. In doing so, the number of parameters on ConnectClientAndServer() started getting tedious, so I've split that into a CreateClientAndServer() and CompleteHandshakes(). Callers that need to configure weird things or drive the handshake manually can call CreateClientAndServer() (which takes care of the BIO pair business) and continue from there. Bug: b/183734559 Change-Id: I05e1edb6d269c8468ba7cde7dc90e0856694a0ca Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47344 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: