| commit | f77c8a38be1f8319b11a71e6cbe5b2694f8871b6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Dec 21 17:58:36 2018 -0600 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Jan 03 21:02:24 2019 +0000 |
| tree | d734a7dcb708b8c097d023fac3feb5df45c389f1 | |
| parent | cc5a888fe5987be93542588d31704f3f446e1c56 [diff] |
Be less clever with CHECK_ABI. Unwind testing will make CHECK_ABI much slower. The original ptrace-based design is some 10,000x slower. I've found an alternate design that's a mere 1,000x slower, but this probably warrants being more straightforward. It also removes the weirdness where NDEBUG controlled which tests were run. While it does mean we need to write some extra tests for p256-x86_64.pl, we otherwise do not directly unit test our assembly anyway. Usually we test the public crypto APIs themselves. So, for most files, this isn't actually extra work. Bug: 181 Change-Id: I7cbb7f930c2ea6ae32a201da503dcd36844704f0 Reviewed-on: https://boringssl-review.googlesource.com/c/33965 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.
There are other files in this directory which might be helpful: