commit | 8fcc755cf5a39149e135e561cb8349c513b5ae05 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Aug 18 13:42:19 2016 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Aug 18 18:14:21 2016 +0000 |
tree | 99cd590e894c47db29f36f556912f2de12ee33c3 | |
parent | 8a8349b53eb22bc1636444768a4e39f3c2b58551 [diff] |
Don't add ERR_R_INTERNAL_ERROR to BN_R_NO_INVERSE. This was causing some Android breakage. The real bug is actually entirely in Android for getting its error-handling code wrong and not handling multiple errors. I'll fix that. (See b/30917411.) That said, BN_R_NO_INVERSE is a perfectly legitimate reason for those operations to fail, so ERR_R_INTERNAL_ERROR isn't really a right thing to push in front anyway. We're usually happy enough with single-error returns (I'm still a little skeptical of this queue idea), so let's just leave it at that. Change-Id: I469b6e2b5987c6baec343e2cfa52bdcb6dc42879 Reviewed-on: https://boringssl-review.googlesource.com/10483 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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: