commit | ad36a4fc4a825b7874fde30c95a196b71ae044a8 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sat Apr 13 17:40:13 2024 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 22 15:46:08 2024 +0000 |
tree | c702378349eeee6622e851f21ef8b96341950890 | |
parent | 0aa300b9ba9d66b914793ad18c5b469163e58905 [diff] |
Make SSL_CTX_set_keylog_callback constant time We encode the secrets in hex. When we do so, we should not leak them based on memory access patterns. Of course, the caller is presumably going to leak them anyway, because this is the SSLKEYLOGFILE callback. But it's plausible that the caller might have registered the callback unconditionally and then, in the callback, decide whether to discard the data. In that case, we should not introduce a side channel. Change-Id: If6358a3081c658038232b4610603967cb38659b4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/67829 Reviewed-by: Bob Beck <bbe@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:
There are other files in this directory which might be helpful: