| commit | 2c0cc6c95e36224f1713cc00a1b5cea43b9fba10 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Sep 12 22:09:13 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 19 17:32:59 2024 +0000 |
| tree | 71efc30e0c0299714f43cbb6911f8b666d2db073 | |
| parent | 59c222fcf123ec2026da450a0a8676436751a351 [diff] |
runner: Remove block pool runner is a fork from a very old version of Go's crypto/tls. Back then, crypto/tls implemented some pooled memory thing to reduce allocations. The abstraction is pretty confusing. Replace it with (I think) more idiomatic patterns using []byte and bytes.Buffer. As part of this, I've moved things common to TLS and DTLS into the encrypt method so encrypt is now responsible for generating the explicit IV and adding TLS 1.3 padding. Change-Id: I21527dd406d2691bc5d24378a832114c43b8b753 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71367 Reviewed-by: Nick Harper <nharper@chromium.org> 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: