| commit | fb1c75caf8ba5d45a0f2c52facd36e4ad9289549 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu May 30 15:29:58 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 04 23:57:36 2024 +0000 |
| tree | 9673e2ba29fb78bd804261421ed01783a7686f96 | |
| parent | e491eeb610fcc69b98bc6d1ba08faf78655808f6 [diff] |
Test various empty string cases with NPN callbacks NPN is a little odd, owing to being a three-step process. The client offers NPN, then the server accepts NPN and offers a list of protocols, then the client picks a protocol. The server is permitted to accept NPN but then offer zero supported protocols. This worked, but was not tested or clearly documented. In the last step, the client *must* pick a protocol, but it is permitted to pick the empty string. The semantics of this are not explicitly stated in the draft, but one can infer it means we aren't picking a protocol. This also worked but was not tested or clearly documented. Change-Id: I26d7089f4902834ff68a97467fc826e957d5fdf8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/69027 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@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.
Project links:
There are other files in this directory which might be helpful: