| commit | 823effe97507d036f660c6c65203f7551d5f0a99 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Wed Jan 16 11:47:47 2019 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jan 16 20:02:16 2019 +0000 |
| tree | a151ac2763d94f4f1b01d857e43c51a5d16dc0bd | |
| parent | 73b1f181b661cd5cb52be6165fccb5270e6e1753 [diff] |
Revert "Fix protos_len size in SSL_set_alpn_protos and SSL_CTX_set_alpn_protos" This reverts commit 35771ff8afc2201b5cf5b884db5b3889edde06bc. It breaks tcnetty, which is tcnetty's fault but we have a large backlog from Christmas to break with at the moment. Bug: chromium:879657 Change-Id: Iafe93b335d88722170ec2689a25e145969e19e73 Reviewed-on: https://boringssl-review.googlesource.com/c/34324 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: David Benjamin <davidben@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: