| commit | 073391f7d69da2d94e06d087224f924fb6d33144 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed May 03 15:03:35 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed May 03 19:15:47 2017 +0000 |
| tree | 0056021df3d9ac2435ddb4d90bb52544e7e252c6 | |
| parent | be5c67d4b1b71ebe3dec1c39a0a8e4e05f66f021 [diff] |
Detach encrypt and keygen hooks from RSA_METHOD. Nothing is using them. For encrypt, there's generally no need to swap out public key operations. keygen seems especially pointless as one could just as easily call the other function directly. The one behavior change is RSA_encrypt now gracefully detects if called on an empty RSA, to match the other un-RSA_METHOD-ed functions which had similar treatments. (Conscrypt was filling in the encrypt function purely to provide a non-crashing no-op function. They leave the public bits blank and pass their custom keys through sufficiently many layers of Java crypto goo that it's not obvious whether this is reachable.) We still can't take the function pointers out, but once https://github.com/google/conscrypt/commit/96bbe03dfd2737f0c1461db59966ff41502a91e4 trickles back into everything, we can finally prune RSA_METHOD. Bump BORINGSSL_API_VERSION as a convenience so I can land the corresponding removal in Conscrypt immediately. Change-Id: Ia2ef4780a5dfcb869b224e1ff632daab8d378b2e Reviewed-on: https://boringssl-review.googlesource.com/15864 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: