| commit | 860cc73bb2964457461a6f3cb5807dbd79256372 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sun Mar 12 12:42:33 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 16 16:28:09 2023 +0000 |
| tree | 5c4dee0eecff59d984510bcd06a64be11e4d1d07 | |
| parent | 6a231e5c6e2b299da0be16e1edbb0195265afec3 [diff] |
Reduce type-punning in ASN1_TYPE ASN1_TYPE is a union of a bunch of pointer types. Often it takes a shorthand and accesses a->value.ptr directly. This is allowed in C, but not C++. Writing the switch/case barely takes more code, so just write it that way. Along the way, extract the code for cleaning up an ASN1_TYPE from tasn_fre.c. This is a small step towards being able to use crypto/asn1's types without depending on the templates. ASN1_TYPE_free still, for now, calls into the templates. That will be fixable once tasn_*.c are rewritten a bit further. This also removes the weird hack here ASN1_primitive_free (an internal function) with NULL ASN1_ITEM secretly meant to partially clean up the ASN1_TYPE. We can just call the function directly now. Bug: 574 Change-Id: Ie2ba41418801a366ab2f12eccc01e8dadf82c33e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/58126 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: