| commit | 9eaa3bd55d5d7836f56051bf87c051ae6890ca06 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Sep 27 17:03:54 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 27 21:58:05 2017 +0000 |
| tree | e84583a9dc29e836be28ee7f189b5e16f381b986 | |
| parent | 73d42e614c21b3ec173c839bf1f687f1654b4265 [diff] |
Remove SSL_CTX_sessions and properly lock SSL_CTX_sess_number. SSL_CTX_sessions is the only think making us expose LHASH as public API and nothing uses it. Nothing can use it anyway as it's not thread-safe. I haven't actually removed it yet since SSL_CTX is public, but once the types are opaque, we could trim the number of symbols ssl.h pulls in with some work. Relatedly, fix thread safety of SSL_CTX_sess_number. Change-Id: I75a6c93509d462cd5ed3ce76c587f0d1e7cd0797 Reviewed-on: https://boringssl-review.googlesource.com/20804 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: