| commit | 1a7233d191952cc163133a5ab235a0ab0f31c812 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Nov 12 10:17:56 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Nov 21 15:40:31 2023 +0000 |
| tree | e9ed9602f866048b71c7994707e5730bc4bb6e3e | |
| parent | a697bcb71dc1b822e681fc3defb61786f6c26c2e [diff] |
Unexport some ASN1_ITEMs that aren't used externally The only ASN1_ITEMs from x509.h that are referenced externally are X509_NAME, X509_ALGOR, and RSA_PSS_PARAMS. (RSA_PSS_PARAMS only by way of an ASN1_item_pack call.) The others don't actually need ASN1_ITEMs. This will cut down on the number of compatibility schemes we need when the parsers are rewritten. Also remove (d2i|i2d)_X509_NAME_ENTRY. It seems people only need to create and destroy them, not serialize them individually. It also means we can actually remove X509's ASN1_ITEM, as it's already unused inside the library. I've replaced EmbedX509 with tests for the types that are actually embedded. Those have not yet been rewritten, but the tests are now ready for when they are. Update-Note: Fewer types can be parsed generically through the ASN1_ITEM system now. If someone was relying on a removed ASN1_ITEM, it will appear as a compile error and we can restore it. Bug: 443 Change-Id: Ib2a75d40c2e93dcf1c0474cf0df4a96190aac9a4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63946 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@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: