commit | 89973806bc2ef652189e157f2736a7d32229c404 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue May 13 13:24:48 2025 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 13 11:13:04 2025 -0700 |
tree | 37c07fccc29fd3bc715c5dda2a473ff8c676a363 | |
parent | 2a514a51baebd5a232fc64f7b082f7a8b28cd29d [diff] |
Tidy up some comments and #defines around salt lengths https://boringssl-review.googlesource.com/c/boringssl/+/79267 will bump the PKCS5_SALT_LEN constant to 16. To avoid some confusing results from that: 1. Don't bother using a constant for EVP_BytesToKey (a generalized PBKDF1). It's not really doing anything there, since the public API just says 8 anyway. 2. Fix the structure citation from PKCS #5 (RFC 2898, now RFC 8018) to PKCS #12 (RFC 7292). This is actually the PKCS #12 version of the structure, which has no constraint on the salt length. See https://crbug.com/416889523#comment4 Bug: 416889523 Change-Id: I1aded3bf93c2ffc281b71013a6ea4135d39e28d9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79287 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@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: