Raw Public Keys: Configure cert types accepted from the server To indicate support for Raw Public Keys (RFC 7250), the client may list cert type(s) accepted from the server (the options are RawPublicKey or X.509) in the ClientHello, and the server may list a client cert type accepted from the client in the ServerHello. This CL adds API functions to configure the cert types that the caller wishes to accept from the peer (whether the caller is client or server), and implements the client's sending of the accepted types in server_certificate_type in the ClientHello. (The client_certificate_type extension in the ServerHello, which is also derived from the accepted types on the server side, is implemented later.) Bug: 467663225 Change-Id: I6042fa9a03eb395d85f9c92fd766e2836a6a6964 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/89827 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: 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:
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: