| commit | 352351b5c04b44ef67a4cd1e473a51fcc97010c6 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Sep 04 16:26:32 2020 -0400 |
| committer | Adam Langley <agl@google.com> | Fri Nov 06 19:19:49 2020 +0000 |
| tree | 2667101d8a641ee0ca7c5336e588e866c8543d71 | |
| parent | 1607f54fed72c6589d560254626909a64124f091 [diff] |
Remove sk_new_null call. This entire function is assuming all the STACK_OF(T) types are secretly the same type, but best to consistently use the sk_ASN1_VALUE_* wrappers. The raw sk_foo functions are an implementation detail of the macros and we probably should rename them to be better prefixed (as upstream did). Change-Id: I62d910b93ca6be5e1c83ae269c7df6a437ffb316 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/43884 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: