| commit | 44fd6eeef57e09b49d66035cb2a640c31a156f25 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jan 22 17:30:49 2018 -0500 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 22 23:06:41 2018 +0000 |
| tree | ee24969a1b9d523b2954139bf048f77dc3162c87 | |
| parent | 98e24197ee36e84cb6113f13cc9511d0df0f1ff7 [diff] |
Split BORINGSSL_self_test into its own file. Some non-FIPS consumers exclude bcm.c and build each fragment file separately. This means non-FIPS code cannot live in bcm.c. https://boringssl-review.googlesource.com/25044 made the self-test function exist outside of FIPS code, so it needed to be moved into is own file. To avoid confusing generate_build_files.py, this can't be named self_test.c, so I went with self_check.c. Change-Id: I337b39b158bc50d6ca0a8ad1b6e15eb851095e1e Reviewed-on: https://boringssl-review.googlesource.com/25124 Reviewed-by: Martin Kreichgauer <martinkr@google.com> 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: