| commit | 23e9aec99b00cb9bc5aabb39975341f411c0db55 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Thu Jul 26 11:40:47 2018 -0700 |
| committer | Adam Langley <agl@google.com> | Fri Jul 27 16:45:12 2018 +0000 |
| tree | e460630096ff4ae16c651174e37d434b82950c79 | |
| parent | f3bfab0035fe671889250c1cc52973109bfc104f [diff] |
Support Wycheproof vectors with the curve given in the group. Future versions of the Wycheproof vectors will specify the curve for a group of tests, rather than for each test. This change works with both the old and new style. Change-Id: I0d9a503c8357eb4c617544e727d8f4a703c2c2b0 Reviewed-on: https://boringssl-review.googlesource.com/30084 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: