commit | 6e3f5cc7e16b8ab1b0a924c60f14332cb1697217 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Sep 14 14:43:14 2016 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 14 19:20:33 2016 +0000 |
tree | 1e89e8d602164783945cf50080cf3007190ac9ab | |
parent | bb5484049dc20915a439a4c0aaca79e67c796df6 [diff] |
Add SSL_CTX_get_keylog_callback. Conscrypt would like to write a CTS test that the callback isn't set unexpectedly. Change-Id: I11f987422daf0544e90f5cff4d7aaf557ac1f5a2 Reviewed-on: https://boringssl-review.googlesource.com/11060 Reviewed-by: Kenny Root <kroot@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@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: