| commit | 4f75b76ef294a5a2c3b7693505f90b142fb1c9e5 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Thu Dec 17 14:06:25 2020 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 06 17:28:02 2021 +0000 |
| tree | 55b50ace187a3944bec801831b4e58333536d7b6 | |
| parent | 9422ac61f71c818e5725e1bcb9615d701d2f1bc1 [diff] |
acvp: add tests This change causes the run_tests target, in FIPS builds, to run ACVP for each supported algorithm. For most of them the output can be compared against a known result. For some of them the output is too variable and they are only run to ensure that they don't have local errors. The ACVP test vectors have been trimmed significantly because they're often huge. Firstly an included tool drops all but one test from each group. Some vector sets have been manually trimmed to remove tests that cause variable output. Change-Id: Iff73851e3d47813041cc7ea6d881282750274940 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/44746 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@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.
Project links:
There are other files in this directory which might be helpful: