| commit | 54afdab5846572b69f8a3bd24d1f6d622268060d | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 30 13:16:59 2016 -0400 |
| committer | Adam Langley <agl@google.com> | Fri Sep 30 19:13:36 2016 +0000 |
| tree | 8b094dd68609f95b8ae8f88609ea1b94b98afc83 | |
| parent | 31f5b3c605617f7b1ffc1c9ab23fc539377fa7ba [diff] |
Fix X509_CRL construction under malloc failures. If asn1_item_ex_combine_new fails in one of the ASN1_template_new calls just before the ASN1_OP_NEW_POST call, ASN1_item_ex_free will free the temporary object which ultimately calls ASN1_OP_FREE_POST. This means that ASN1_OP_FREE_POST needs to account for zero-initialized objects. Change-Id: I56fb63bd5c015d9dfe3961606449bc6f5b1259e3 Reviewed-on: https://boringssl-review.googlesource.com/11403 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.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: