commit | 84cd159badd399847703da2c0c68cee8e405b3e1 | [log] [tgz] |
---|---|---|
author | Adam Langley <alangley@gmail.com> | Thu Jun 30 18:29:44 2016 -0700 |
committer | Adam Langley <alangley@gmail.com> | Fri Jul 01 21:46:53 2016 +0000 |
tree | 98921ace316e8d330ae5496d824dc99a9e516fae | |
parent | b72f66f59cc5c8db51f6b60f2f5b97b56dc372f3 [diff] |
Add SSL_CTX_up_ref. Upstream added this in a18a31e49d266. The various *_up_ref functions return a variety of types, but this one returns int because upstream appears to be trying to unify around that. (See upstream's c5ebfcab713.) Change-Id: I7e1cfe78c3a32f5a85b1b3c14428bd91548aba6d Reviewed-on: https://boringssl-review.googlesource.com/8581 Reviewed-by: Adam Langley <alangley@gmail.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: