commit | 3e8b782c0cc0d9621f622cf80ab1a9bcf442fa17 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Feb 15 20:09:09 2017 -0500 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Feb 16 23:04:15 2017 +0000 |
tree | cbda897319d79e8a31a12ef5f8c7663d4d230746 | |
parent | 628f518cdc46726b3159aaa7ea4f6b48f6890f7f [diff] |
Remove "raw" versions of PKCS8_encrypt and PKCS8_decrypt. These were added in an attempt to deal with the empty vs. NULL confusion in PKCS#12. Instead, PKCS8_encrypt and PKCS8_decrypt already treated NULL special. Since we're stuck with supporting APIs like those anyway, Chromium has been converted to use that feature. This cuts down on the number of APIs we need to decouple from crypto/asn1. BUG=54 Change-Id: Ie2d4798d326c5171ea5d731da0a2c11278bc0241 Reviewed-on: https://boringssl-review.googlesource.com/13885 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: