|author||David Benjamin <email@example.com>||Mon May 09 17:45:18 2022 -0400|
|committer||Boringssl LUCI CQ <firstname.lastname@example.org>||Tue May 10 15:22:01 2022 +0000|
Implement SSL_CTX_set_num_tickets. CPython and wpa_supplicant are using this nowadays. To avoid needing to tweak the ticket nonce derivation, I've just internally capped the number of tickets at 16, which should be plenty. Change-Id: Ie84c15b81a2abe8ec729992e515e0bd4cc351037 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52465 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: David Benjamin <firstname.lastname@example.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: