| commit | 8aae8a126bbf9a5d5271e81179eb9d1138b4b1df | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Aug 26 15:21:06 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Fri Aug 26 19:28:56 2016 +0000 |
| tree | adcf3f4df863c9ec8bd54fd971733a4fa37b1843 | |
| parent | 1db42fb3ca46d3d4987ddae2f7aec7732c66a70b [diff] |
Remove M_i2d_* and M_d2i_*. Somehow I didn't notice these used i2d_ASN1_bytes and d2i_ASN1_type_bytes when removing those. Fortunately the macros are also removable so drop them too. Change-Id: I2a7b198eab2d3811e5ced1f347597185b4697f8d Reviewed-on: https://boringssl-review.googlesource.com/10660 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: