| commit | 9b885c5d0fe1a89b2063654dbdd0faf2a6c076fd | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Fri Nov 18 14:21:03 2016 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Nov 19 00:24:18 2016 +0000 |
| tree | b2b7a2166c7e65f926db50407e6e0268259476cb | |
| parent | 6f5f49f33d88f446f7f690bf991e835d5137af6c [diff] |
Don't allow invalid SCT lists to be set. This change causes SSL_CTX_set_signed_cert_timestamp_list to check the SCT list for shallow validity before allowing it to be set. Change-Id: Ib8a1fe185224ff02ed4ce53a0109e60d934e96b3 Reviewed-on: https://boringssl-review.googlesource.com/12401 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> 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.
There are other files in this directory which might be helpful: