| commit | 42d9a13df20d7b005ca0e9d646a47c14cae7ad85 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Sep 29 22:01:08 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 30 05:44:51 2025 -0700 |
| tree | ae9f71df315478230abe32b106120903b92b04e2 | |
| parent | b2a2955da7ed3190f099817b8e3daabe322a1078 [diff] |
Put the legacy cipher constants back in tls1.h and ssl3.h QUICHE expects TLS1_CK_* to be defined in tls1.h, not ssl.h. For now, just define them in tls1.h as before. Ideally we'd define them in terms of the other constants, but we'd then either need to move SSL_CIPHER_* out of ssl.h or merge tls1.h and ssl3.h into ssl.h. The latter is probably a better direction, but is a much larger change, so start with this. This should unbreak the Chromium roll. Change-Id: Ic403bef7043028d30aa9916b403ebb3721734f32 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82387 Auto-Submit: David Benjamin <davidben@google.com> Reviewed-by: Lily Chen <chlily@google.com> Commit-Queue: Lily Chen <chlily@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: