|author||David Benjamin <email@example.com>||Tue Jun 12 13:23:41 2018 +0000|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Jun 12 13:23:55 2018 +0000|
Reland "Revert "Add other Windows configurations to the CQ."" This reverts commit 23e92d5d1646b2fe46d1765fd1a78ab813dc5dc8. Reason for revert: Nope. Still doesn't work. Back to poking infra about it... Original change's description: > Revert "Revert "Add other Windows configurations to the CQ."" > > This reverts commit 98831738f22c36d8e9a5cc8fc2e07453bed30074. > > Let's try this again. tandrii@ says this should be resolved as of > https://crbug.com/840505. (That was a while ago. I'd forgotten about > it.) > > Change-Id: Ib49a629198a33d44ff1c3aa13af5825def1a5c4d > Reviewed-on: https://boringssl-review.googlesource.com/28924 > Reviewed-by: Steven Valdez <firstname.lastname@example.org> > Commit-Queue: Steven Valdez <email@example.com> > CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> TBRfirstname.lastname@example.org,email@example.com Change-Id: Iecd0710075f1fedc4dea69283d018042fb1a2490 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://boringssl-review.googlesource.com/29104 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.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: