|author||David Benjamin <firstname.lastname@example.org>||Sat Apr 15 18:12:55 2017 -0400|
|committer||Adam Langley <email@example.com>||Mon May 22 15:06:04 2017 +0000|
Convert stack.h to use inline functions. Instead of a script which generates macros, emit static inlines in individual header (or C files). This solves a few issues with the original setup: - The documentation was off. We match the documentation now. - The stack macros did not check constness; see some of the fixes in crypto/x509. - Type errors did not look like usual type errors. - Any type which participated in STACK_OF had to be made partially public. This allows stack types to be defined an internal header or even an individual file. - One could not pass sk_FOO_free into something which expects a function pointer. Thanks to upstream's 411abf2dd37974a5baa54859c1abcd287b3c1181 for the idea. Change-Id: Ie5431390ccad761c17596b0e93941b0d7a68f904 Reviewed-on: https://boringssl-review.googlesource.com/16087 Reviewed-by: Adam Langley <firstname.lastname@example.org>
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.
There are other files in this directory which might be helpful: