|author||David Benjamin <firstname.lastname@example.org>||Mon Apr 15 12:54:01 2019 -0500|
|committer||Adam Langley <email@example.com>||Mon Apr 15 21:55:06 2019 +0000|
Fix EVP_CIPHER_CTX_copy for AES-GCM. 7578f3f0dea091a3392f0be3216989bdc7355ad2 made it work, but 26ba48a6fbbf7b25bbfb521d3f5591e2d5a0b4bd regressed it by losing the EVP_CIPH_CUSTOM_COPY flag. Additionally, we've since added an alignment requirement to EVP_AES_GCM_CTX, which complicates things. Thanks to Guido Vranken for catching this! Bug: 270 Change-Id: I71784593dc5a34d1334c92a4daa93546ec0ee2c3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35624 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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: