| commit | d55bd797eb2f06c3f89f0df7895ab13f13d6f6c0 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu May 18 11:33:08 2017 -0400 |
| committer | Adam Langley <agl@google.com> | Thu May 18 15:49:31 2017 +0000 |
| tree | 2add25443e6b0687d68a2773ff349cb5ff947106 | |
| parent | 250542312b3e74e068634473a4cd2b63e4ed915d [diff] |
Fix SSL_COMP_get_compression_methods type signature. We returned the wrong type, but with a typedef which made it void*. In C++, void* to T* doesn't implicitly convert, so it doesn't quite work right. Notably, Node passes it into sk_SSL_COMP_zero. The sk_* macros only weakly typecheck right now, but a pending CL converts them to proper functions. Change-Id: I635d1e39e4f4f11b2b7bf350115a7f1b1be30e4f Reviewed-on: https://boringssl-review.googlesource.com/16447 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.
There are other files in this directory which might be helpful: