| commit | 7ce10d5da7c4909a6e44b054c8e0768db03200af | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Mar 14 02:00:46 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Mar 26 00:17:25 2017 +0000 |
| tree | 46442dafcaf5586123efdaa00c4aa5cf267c4868 | |
| parent | 4784b99bf3cb5db20dd03fbecf183d3f9772b2f7 [diff] |
Partially split out crypto/pkcs8's legacy ASN.1 dependencies. PKCS8_encrypt and PKCS8_decrypt still need to be split. The code for processing PKCS#12 files is, for now, placed entirely in pkcs8_x509.c. If we need to split it up, it should be straightforward to do so. (Introduce a CRYPTO_BUFFER version of PKCS12_get_key_and_certs and go from there.) BUG=54 Change-Id: I9c87e916ec29ee14dbbd81c4d3fc10ac8a461f1a Reviewed-on: https://boringssl-review.googlesource.com/14214 Reviewed-by: Steven Valdez <svaldez@chromium.org> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@chromium.org> Commit-Queue: David Benjamin <davidben@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: