| commit | 35771ff8afc2201b5cf5b884db5b3889edde06bc | [log] [tgz] |
|---|---|---|
| author | Raul Tambre <raul@tambre.ee> | Sat Jan 05 22:39:39 2019 +0200 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Jan 07 18:14:42 2019 +0000 |
| tree | e20614fa362dcf19f5389cfba7e01f1a8b257be7 | |
| parent | 9cde848bd1109f1a0a77d68b19732ed5535d6953 [diff] |
Fix protos_len size in SSL_set_alpn_protos and SSL_CTX_set_alpn_protos MakeConstSpan() takes size_t as the second argument, so protos_len ought to also be size_t. Bug: chromium:879657 Change-Id: I93089ea20ce4b9c2b9d4d954dce807feb5341482 Reviewed-on: https://boringssl-review.googlesource.com/c/34164 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: 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: