| commit | 34de91e3771f4d0a8fed2e4a152e8b07d5005151 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Oct 07 00:21:35 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sun Oct 09 17:04:41 2016 +0000 |
| tree | 49c6287fae5d60c1a07bab485e5a9f90ddfca316 | |
| parent | b74b08144ea12adb229d9a4a7855ebfdbb7f7c8c [diff] |
Revise server-side ECDSA certificate checks. This is in preparation for simplifying tls1_check_group_id, called by tls1_check_ec_cert, which, in turn, is in preparation for moving the peer group list to SSL_HANDSHAKE. It also helps with bug #55. Move the key usage check to the certificate configuration sanity check. There's no sense in doing it late. Also remove the ECDSA peer curve check as we configure certificates externally. With only one certificate, there's no sense in trying to remove it. BUG=55 Change-Id: I8c116337770d96cc9cfd4b4f0ca7939a4f05a1a9 Reviewed-on: https://boringssl-review.googlesource.com/11524 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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: