|author||David Benjamin <firstname.lastname@example.org>||Thu Mar 14 18:31:16 2019 -0500|
|committer||Adam Langley <email@example.com>||Mon Mar 18 17:19:12 2019 +0000|
Harden the lower level parts of crypto/asn1 against overflows. The legacy ASN.1 stack contains an unsalvageable mix of integer types. 82dfea8d9e65c4e57cc9fb2bd3f0dd49f5b31f45 bounded all inputs to the template machinery, but sometimes code will call ASN1_get_object directly, such as the just deleted d2i_ASN1_UINTEGER. Thanks to mlbrown for reporting the d2i_ASN1_UINTEGER overflow. Bug: chromium:942269 Change-Id: I2d4c8b7faf5dadd1b68dbdb51a5feae071ea2cb6 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35325 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: