| commit | cdc5c184b3421187d21d73fb19baebcef061063a | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Apr 01 12:13:31 2020 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Apr 01 18:01:12 2020 +0000 |
| tree | 07dcd5adf44ba2f12c81d22c2ae9f7256d95ea8d | |
| parent | 0cf14d3ec8d79b33bdaede1266a8c90595d03a05 [diff] |
Add simpler getters for DH and DSA. These come from OpenSSL 1.1.1. I don't think any third-party code is using them yet, but OpenSSL 1.1.0 is EOL, so newer code may use them and they're much more convenient when porting over existing uses of DH and DSA. Bug: 325 Change-Id: I767496da4b458a3871dea23a1405b1e7e40b3de5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40484 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: