| commit | 740744bc06fd9718c983bc83b61fd13cd428ae2e | [log] [tgz] |
|---|---|---|
| author | Xiangfei Ding <xfding@google.com> | Mon Oct 20 07:54:10 2025 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 24 11:34:38 2025 -0700 |
| tree | f373c335ba133e6423b1e41d1abe52cfa9baf581 | |
| parent | 718fcf91d4e3296c0303f36ccbaa6d5ea363ab32 [diff] |
Update Wycheproof test vectors Source: https://github.com/C2SP/wycheproof Commit: a6e88a9dbb48a7dd577004932f3770cc5335c559 We also - Ignore common developer toolchain local configs and caches - Generate test vectors from Wycheproof - Update test suite with new flags accordingly - Update existing test fixture and unify the test vector schema with the upstream Bug: 42290453 Change-Id: I0a4de95c9689b4892507bd0748c60e804b7900a3 Signed-off-by: Xiangfei Ding <xfding@google.com> Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83087 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: