|author||David Benjamin <email@example.com>||Thu Nov 12 09:25:30 2015 -0800|
|committer||Adam Langley <firstname.lastname@example.org>||Mon Nov 16 23:59:14 2015 +0000|
size_t SSL*_use_*_ASN1. So long as we're not getting rid of them (the certificate variants may be useful when we decouple from crypto/x509 anyway), get the types and bounds checks right. Also reject trailing data and require the input be a single element. Note: this is a slight compatibility risk, but we did it for SSL*_use_RSAPrivateKey_ASN1 previously and I think it's probably worth seeing if anything breaks here. Change-Id: I64fa3fc6249021ccf59584d68e56ff424a190082 Reviewed-on: https://boringssl-review.googlesource.com/6490 Reviewed-by: Adam Langley <email@example.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: