commit | 124122878245e9c3be5ad9e625a1af447236169e | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Thu Jun 03 18:05:40 2021 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 07 21:00:07 2021 +0000 |
tree | 0bcba930bbd20224fcdc9a9979dcf1b6ba30594b | |
parent | 88df13d73d5a74505f046f0bf37fb2fb3e1f1a58 [diff] |
runner: Revise ECHConfig type in preparation for client implementation An ECHConfig is like a certificate in that knowing the fields isn't sufficient. The exact byte representation is significant. (The ECHConfig is bound into the encryption.) But the ECHConfig type only has fields, so runner can only represent ECHConfigs that are the output of our serialization function. This matters less as a client testing a server because the server can only parse ECHConfigs with fields we support. But as a server testing a client, we need to see how the client reacts to extra extensions, etc. Just using []byte to represent ECHConfigs is inconvenient, so instead pattern this after x509.Certificate: you can parse one from a byte string (not currently included since we don't need it yet), or you can construct a new one from a template with the fields you want. Bug: 275 Change-Id: I6602d0780b1cef12b6c4b442999bdff7b3d7dd70 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/47964 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.
Project links:
There are other files in this directory which might be helpful: