commit | eda849d2e6e6a15a5a4dc728568ec12f21ebfb6d | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Jul 06 18:21:36 2020 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jul 08 16:09:11 2020 +0000 |
tree | 6fbb5ef0fc754b2bb9d7d01c351894b743c6610a | |
parent | 5d7c2f8b1d2643856c74d63c5b455a5c0828bd83 [diff] |
Opaquify PKCS8_PRIV_KEY_INFO. This is partially imported from upstream's 54dbf42398e23349b59f258a3dd60387bbc5ba13 which does something similar. In doing so, remove the pkcs8->broken field, which is a remnant of some parsing hacks we long since removed (PKCS8_set_broken). The immediate motivation is, if this sticks, this would make it easier to detach i2d_PKCS8_PRIV_KEY_INFO and d2i_PKCS8_PRIV_KEY_INFO from the old ASN.1 code. Update-Note: Direct accesses of PKCS8_PRIV_KEY_INFO now need to use the accessors. Code search suggests no one uses the fields. Even the accessors are virtually unused (the one thing which uses it doesn't need it). Bug: chromium:1102458 Change-Id: I57054de3fe412079f7387dc99291250e873b1471 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42006 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.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.
Project links:
There are other files in this directory which might be helpful: