Add ASN1_BIT_STRING_unused_bits and deprecate ASN1_BIT_STRING_num_bytes This is much more straightforward. ASN1_BIT_STRING_num_bytes was more complex because it needed to account for the byte count dynamically shrinking. Also remove the internal asn1_bit_string_length as this is no longer needed. OpenSSL 4.x currently has a much more complex, fallible, two-out-param function, ASN1_BIT_STRING_get_length. We can implement that for compatibility later, but let's see if OpenSSL would be interested in a simpler API first. I've filed https://github.com/openssl/openssl/issues/30809 Bug: 42290311 Change-Id: I0427ff8c42b61d64466e30ea5af425097703048d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/92569 Reviewed-by: Lily Chen <chlily@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: