| commit | 193edd58a51d9649d5ab3b89a8c6fe5bdd70f9c0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jun 19 15:03:04 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jul 07 14:38:08 2025 -0700 |
| tree | 3d64938c7b37db2378219cf59fbc3e7910df0846 | |
| parent | 3fd8220e3c88365627ecd1af7c29f5096ff9cefd [diff] |
runner: write a new test certificate library This is a test certificate library that is slightly more convenient to build certificate chains. More importantly, it reimplements the crypto/x509 serializer with x/crypto/cryptobyte. This is a fair amount of work, but means we can add new key types that Go does not support, notably RSA-PSS keys. This is to ensure that later work to add RSA-PSS keys to libcrypto (but *not* libssl) will not regress libssl. (All this work to test that we *don't* support something in libssl.) Bug: 384818542 Change-Id: I54cd264cf9e774fc38d8f8780becb61f886466a3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80267 Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: 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: