| commit | bef6cc29338a693634092ca8f68902a3a9e26113 | [log] [tgz] |
|---|---|---|
| author | Phillipp Schoppmann <schoppmann@google.com> | Tue Sep 11 12:02:05 2018 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Sep 11 16:35:22 2018 +0000 |
| tree | b3ed7a0ea805e819b6238d04536a380545c5515c | |
| parent | 695e589b0c8957680cac36468cf3e0fb56f9ef8f [diff] |
Fix check of the pointer returned by BN_CTX_get The check of `r` instead of `rr` was introduced in change I298400b988e3bd108d01d6a7c8a5b262ddf81feb. Change-Id: I4376a81c65856f6457b0a11276176bf35e9c647d Reviewed-on: https://boringssl-review.googlesource.com/31844 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: