Raw Public Keys: Configure and advertise available client cert types This CL adds a new SSL_CREDENTIAL type for Raw Public Keys. This type of credential must have a public key and (either a private key or private key method) configured in order to be considered complete. This CL implements advertising the caller's available cert types (as a client) in the client_certificate_type extension in ClientHello. By default, this is automatically populated based on the configured credential list. The caller, as a client, may also configure the credential list late, or may want to deviate from the the available client_certificate_types computed by default. For such cases, this CL also adds an API function to explicitly configure available client cert types offered in the ClientHello. Advertising the server_certificate_type extension in ServerHello, which depends on the configured credential list as well as other decisions, is implemented later. Bug: 467663225 Change-Id: I36da8c1a135cfb423155cf9c7b8d8dc06a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/89829 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: Lily Chen <chlily@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: