commit | a11277e187e407d0ef403b8a60d9a32eaab7d301 | [log] [tgz] |
---|---|---|
author | Nabil Wadih <nwadih@google.com> | Tue Jun 04 11:09:00 2024 -0700 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 20:29:55 2024 +0000 |
tree | 23c1dac15b21ebfb30f02784d0d16184fb5c7b18 | |
parent | 25cf1bb965ba9ae0302cbc6de4ff4dd6cdbbc016 [diff] |
remove un-needed muts which were causing build warnings/errors These were introduced in https://boringssl-review.googlesource.com/c/boringssl/+/68748 and detected in our CI which runs against the boringssl rust bindings at HEAD Change-Id: I42b37e8738baadffbc0c58e0340144685dd04977 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/69007 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: 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.
Project links:
There are other files in this directory which might be helpful: