|author||David Benjamin <firstname.lastname@example.org>||Wed Apr 10 17:03:42 2019 -0500|
|committer||Adam Langley <email@example.com>||Thu Apr 11 15:31:38 2019 +0000|
Add missing nonce_len check to aead_aes_gcm_siv_asm_open. Test invalid nonce lengths more thoroughly to cover this case on all our AEADs. Thanks to Guido Vranken for catching this! In doing so, this also reveals we have a ton of redundant error codes (https://crbug.com/boringssl/269). I'll tidy that up in a separate change as it may require some changes to code in Android. For now, this change uses CIPHER_R_UNSUPPORTED_NONCE_SIZE just to be consistent with the rest of that file. Bug: 268 Change-Id: I0a479000ec3005ee55c828eaa92c8302b4625847 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35545 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: