| commit | b6155e60f3eab82ce35c27de90b642f59d26598b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Fri Dec 25 00:58:34 2015 -0500 |
| committer | Adam Langley <alangley@gmail.com> | Thu Jan 28 00:29:34 2016 +0000 |
| tree | ef6ce8dd100d230d134c0c49d0dcc32b00b435ec | |
| parent | 4e98e5c903785a96a3e263a892941e90af56cb5f [diff] |
Remove app_data from EVP_PKEY_CTX. It's never used. It's not clear why one would want such a thing. EVP_PKEY_CTX has no way for callers to register callbacks, which means there shouldn't be a way for the library to present you an EVP_PKEY_CTX out-of-context. (Whereas app_data/ex_data makes sense on SSL because of its numerous callbacks or RSA because of RSA_METHOD.) Change-Id: I55af537ab101682677af34f6ac1f2c27b5899a89 Reviewed-on: https://boringssl-review.googlesource.com/6849 Reviewed-by: Adam Langley <alangley@gmail.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.
There are other files in this directory which might be helpful: