| commit | d09962d5c30fb0946377d46372eb02ff2cc7d7b9 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Mon Jan 25 11:28:08 2021 -0800 |
| committer | Adam Langley <agl@google.com> | Wed Jan 27 15:31:39 2021 +0000 |
| tree | 2d184aefd8dbd0ff0ffc28e1cb5cb44217895cf5 | |
| parent | e133345dbad0ecb6ec74f293b451b2b3ad7a7bf3 [diff] |
acvp: update to newer FFDH test. Revision 1.0 is this test is reportedly no longer acceptable and we have to use the “SSC” version now. The documentation for this test doesn't mention that a “z” field is possible, but that's what the test vectors from the demo server contain and, after guessing at the correct response format, this makes the NIST server happy. Change-Id: Ic63d9e19998dc015733d847cd0330a3af1d5e7e6 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45224 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: