Fix an OK but odd-looking use of ASN1_TYPE X509_REQ_print_ex accessed an ASN1_TYPE's value.asn1_string union arm before checking the type was an ASN1_STRING-based type. This is fine[*] because it doesn't dereference the pointer until after the type is checked. Nonetheless, we can simply move the access slightly further down to make it more straightforwardly correct. While I'm here: - Use the accessors for ASN1_STRING. One less thing to touch when ASN1_STRING becomes opaque later. - There's no need for the cast. BIO_write already takes void* - While they're all typedefs, accesssing the field as ASN1_BIT_STRING is bizarre when this function does not accept ASN1_BIT_STRING anyway! [*] Strictly speaking, it relies on the more lax C union rules, which allow type-punned direct (but not pointer) access to an inactive union arm. C++ does not allow this, but AIUI every C++ compiler takes the C interpretation in practice. Change-Id: I675b828680a70cbcb540308d3c5dc628b6ad0c48 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88047 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> Auto-Submit: 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: