commit | bc118ee64cf76b9ab695b71f63fffc101e1bdb4d | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Jul 10 17:27:45 2018 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Jul 14 03:50:40 2018 +0000 |
tree | e9a6913f554b87b9abdfc4a3fa27805c7ec128c1 | |
parent | 0a3e07ac1d139eb92b775190d0d1bc88b9da6167 [diff] |
Add SSL_get0_peer_verify_algorithms. Callers who use SSL_get0_certificate_types today will find an empty list in TLS 1.3, which removed it. To provide feature parity, add an accessor for the signature algorithms list. SSL_get_signature_algorithm_key_type can be used to map it to a key type. "Peer signature algorithms" was already taken in the public API by SSL_get_peer_signature_algorithm to refer to which the peer selected, so I named this matching SSL_CTX_set_verify_algorithm_prefs. Change-Id: I12d411d7350e744ed9f88c610df48e0d9fc13256 Reviewed-on: https://boringssl-review.googlesource.com/29684 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Vartanian <flooey@google.com> Reviewed-by: Steven Valdez <svaldez@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.
There are other files in this directory which might be helpful: