| commit | 5358cb50446ff38d7b41e84274bc36582cced621 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Jun 11 23:34:00 2021 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 14 17:59:52 2021 +0000 |
| tree | 9bf229ad4b126eed8ad1bb60793f4dfba2ba52bc | |
| parent | 878795cac3947f37e7852122ebaf53e7c420d69a [diff] |
runner: Check the test name against the protocol being tested. This would have caught an issue with some tests I was working on. It also catches an issue with some per-message tests, so fix those. Change-Id: I6b3ad8e0db0b1a6ccac4b346dcc652b16b73e006 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48046 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@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: