commit | 71573dc40bea04ee918d186376be0814fe9ce384 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon May 23 11:21:04 2022 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 24 00:14:22 2022 +0000 |
tree | 9ebef46c30030537fd62fdf240439792a8d1304f | |
parent | 118a892d2da8c78b46ed549454b3b62ded8c84b7 [diff] |
Clean up ECDSA EVP_PKEY_CTRL_MD validation. We have no EVP_MDs with type NID_ecdsa_with_SHA1 (that's a remnant of the old signature algorithm EVP_MDs). Also there's no sense in calling EVP_MD_type or performing the cast five times. Change-Id: I7ea60d80059420b01341accbadf9854b4c3fd1b8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52685 Reviewed-by: Adam Langley <agl@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: