| commit | e1049fd88d8c0116b3e060eb40898f55a0b299b0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Oct 21 11:38:48 2021 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Oct 21 18:25:47 2021 +0000 |
| tree | 0c90d104ecc7b4f291a88adc0e9b1251aea5ed8e | |
| parent | d2d1d3c6a0a294eb3eaca4112acdfdeffba6933c [diff] |
Fully unexport X509_VAL. After https://boringssl-review.googlesource.com/c/boringssl/+/45965, X509_VAL became largely unusable. While it did still exist as an ASN1_ITEM and we emitted d2i/i2d/new/free functions, there is no way to access its contents. Thus, hide it entirely. Interestingly, although we got that to stick a while ago, I missed that OpenSSL actually keeps X509_VAL exported, so it's possible we'll find 3p code that uses this later. Since a standalone X509_VAL isn't especially useful to construct or encode, this is most likely to come up in code defining new types with <openssl/asn1t.h>. Still, if we need to rexport this later (revert this *and* bring back the struct), it won't be a big deal. Nothing in the public API even constrains X509 to use X509_VAL. Update-Note: The last remnants of the now (barely usable) X509_VAL are no longer exported. It is unlikely anyone was relying on this. Bug: 425 Change-Id: I90975f2f7ec27753675d2b5fa18b5cc4716319f4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/50085 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: