| commit | 1eb7769e1189f90e41b81118d903090dbbe98ea6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri May 07 14:32:39 2021 -0400 |
| committer | David Benjamin <davidben@google.com> | Mon May 10 22:02:08 2021 +0000 |
| tree | 3ff03d2c1c071fddee02203efa90a326d6d6ccaf | |
| parent | 1d58cd1fd3b242910ec1371fab82c9e6a96d7089 [diff] |
Refer to EVP_HPKE_CTX by a consistent name. It's sometimes hpke and sometimes ctx. Our other EVP_FOO_CTX types are usually called ctx, so use ctx. Bug: 410 Change-Id: Ib1c6d8018ffd8fd180b89f5be58283f3f098e44b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47404 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: