| commit | 485c7253196a77d419a8535f117d0b0beaf7f4cc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jan 22 14:46:15 2025 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 22 12:44:35 2025 -0800 |
| tree | a8632f7feeb41a50d2b47c786a9d594015d548bb | |
| parent | 46364fb1aab39c8d9cbd88060dd53165c0ea42c8 [diff] |
Reword the SSL_export_keying_material docs slightly The reference to TLS 1.2's "master secret" (renamed to "main secret" in rfc8446bis, but we haven't applied that yet) is wrong anyway because it's derived from a different secret in TLS 1.3. Even in TLS 1.2, it's misleading because TLS 1.2 resumptions share the master secret, but EKM still exports different values by incorporating the client/server randoms. Change-Id: I21cb4f5ddde9d9fb520c770ca6a89c56daecef6b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75509 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: 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: