| commit | 02084ea3988446273558881a7e728b04d7338350 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Mar 14 02:26:10 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Mar 26 04:00:26 2017 +0000 |
| tree | 5533f1e150e0bcb78dafd2e1140ba5f7632d7939 | |
| parent | 3cb12467ccf1ccbad0adcb909f58916c9688b637 [diff] |
Decouple PKCS8_encrypt and PKCS8_decrypt's core from crypto/asn1. These will be used by Chromium's crypto::ECPrivateKey to work with EncryptedPrivateKeyInfo structures. Note this comes with a behavior change: PKCS8_encrypt and PKCS8_decrypt will no longer preserve PKCS#8 PrivateKeyInfo attributes. However, those functions are only called by Chromium which does not care. They are also called by the PEM code, but not in a way which exposes attributes. The PKCS#12 PFX code is made to use PKCS8_parse_encrypted_private_key because it's cleaner (no more tossing X509_SIG around) and to ease decoupling that in the future. crypto/pkcs8's dependency on the legacy ASN.1 stack is now limited to pkcs8_x509.c. BUG=54 Change-Id: I173e605d175e982c6b0250dd22187b73aca15b1a Reviewed-on: https://boringssl-review.googlesource.com/14215 Reviewed-by: David Benjamin <davidben@google.com> 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: