| commit | ea482ed0e7431fd65ed2bb9954c5ce47a6b3fb8f | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Apr 17 01:29:03 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 17 20:07:10 2025 -0700 |
| tree | 93a0f3d6a57d3ef6fb85be6ed2438b5b7a5c07ad | |
| parent | 02a28c138fcd7e86dd28afaf9719014e89f513f8 [diff] |
Switch a bit more of libcrypto to scopers There was no real organization to which files I looked at here. Mostly just bounced around. At some point we'll probably need to set up some more infrastructure though: - For functions to return UniquePtr, they need to stop being C linkage, which is something we want to do anyway. - For types to use UniquePtr, we need to get them out of malloc/free and into the realm of constructors and destructors. That probably means moving some of the helpers from ssl/internal.h to crypto/internal.h. - UniquePtr is not very good at buffers. We should probably move Array Vector, and InPlaceVector to crypto/internal.h. Change-Id: I90ebc917051d354c0e447598f382db6b22eb8813 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78687 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: