| commit | d3440b4d63862cc4462630b5eb10514cd406315f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jul 14 14:52:41 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Jul 15 18:26:45 2016 +0000 |
| tree | fc69cb50bc0f6379041c94cac65de3827413f418 | |
| parent | 0c0b7e1e1f35c23ecaed10fb262403f1b3cf5882 [diff] |
Give SSL_PRIVATE_KEY_METHOD a message-based API. This allows us to implement custom RSA-PSS-based keys, so the async TLS 1.3 tests can proceed. For now, both sign and sign_digest exist, so downstreams only need to manage a small change atomically. We'll remove sign_digest separately. In doing so, fold all the *_complete hooks into a single complete hook as no one who implemented two operations ever used different function pointers for them. While I'm here, I've bumped BORINGSSL_API_VERSION. I do not believe we have any SSL_PRIVATE_KEY_METHOD versions who cannot update atomically, but save a round-trip in case we do. It's free. Change-Id: I7f031aabfb3343805deee429b9e244aed5d76aed Reviewed-on: https://boringssl-review.googlesource.com/8786 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: