commit | ed22bbb42a36ba6878a2e68b34d43036c221e763 | [log] [tgz] |
---|---|---|
author | Adam Langley <agl@imperialviolet.org> | Sat Dec 14 15:04:47 2024 +0000 |
committer | Adam Langley <agl@google.com> | Sat Dec 14 07:08:48 2024 -0800 |
tree | aa859ef05f885c913dbf9310afe6859ef1ee70f2 | |
parent | 23824fa0fed94f4660ffafb15aaea8b317f2c8a6 [diff] | |
parent | cd95210465496ac2337b313cf49f607762abe286 [diff] |
Merge commit 'cd95210465496ac2337b313cf49f607762abe286' into chromium-stable This jumps chromium-stable to M131. In chromium: ```sh % git show branch-heads/6778:./DEPS | grep "^ *'boringssl_revision 'boringssl_revision': 'cd95210465496ac2337b313cf49f607762abe286', ``` Then, since we can no longer just jump branches forwards, thanks to BCID rules, it seems that we have to create a merge commit: ```sh git checkout chromium-stable git merge --no-ff cd95210465496ac2337b313cf49f607762abe286 git push origin HEAD:refs/for/chromium-stable ``` Change-Id: I23dc96b63e7d29aa4cd88e603632b666f8e6b9be
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: