|author||David Benjamin <firstname.lastname@example.org>||Tue Aug 16 02:06:08 2016 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Aug 16 19:45:13 2016 +0000|
Delete d2i_ASN1_bytes and i2d_ASN1_bytes. These functions are unused. Upstream recently needed to limit recursion depth on this function in 81f69e5b69b8e87ca5d7080ab643ebda7808542c. It looks like deeply nested BER constructed strings could cause unbounded stack usage. Delete the function rather than import the fix. Change-Id: I7868080fae52b46fb9f9147543c0f7970d8fff98 Reviewed-on: https://boringssl-review.googlesource.com/10368 Commit-Queue: David Benjamin <email@example.com> Commit-Queue: Adam Langley <firstname.lastname@example.org> Reviewed-by: Adam Langley <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <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: