|author||David Benjamin <firstname.lastname@example.org>||Sat Dec 14 02:04:44 2019 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Dec 16 20:17:51 2019 +0000|
Handle "acceptable" Wycheproof inputs unambiguously. This CL updates the JSON conversion to preserve the flags. A WycheproofResult now captures both "result" and "flags". An "acceptable" test case's validity is determined by its flags. By default, we consider an "acceptable" case as invalid, but a test driver may mark some of them as valid by listing the flags as a parameter. Previously, some Wycheproof tests (I think it was x25519_tests.txt?) did not contain enough information to resolve this unambiguously. This has since been fixed. This also makes the converted files smaller because we no longer expand the flags into comments. Change-Id: I2ca02d7f1b95f250409e8b23c4ad7bb595d77fdf Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39188 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.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: