|author||David Benjamin <email@example.com>||Tue Jan 09 21:44:28 2018 +0000|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Jan 09 21:45:11 2018 +0000|
Revert "Update tools." This reverts commit 9d1f96606cd7af3b8d441fbc5e8d2e69da37c506. Reason for revert: aarch64 bots are breaking for some reason. Original change's description: > Update tools. > > In particular, get the new NDK. Unfortunately, the new clang picks up > an unfortunate change for clang-cl that we now must work around. > > http://llvm.org/viewvc/llvm-project?view=revision&revision=319116 > > Bug: 109 > Change-Id: I091ca7160683e70cd79b5c2b7a4267fea258ec17 > Reviewed-on: https://boringssl-review.googlesource.com/24644 > Reviewed-by: Steven Valdez <firstname.lastname@example.org> > Commit-Queue: David Benjamin <email@example.com> > CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> TBRfirstname.lastname@example.org,email@example.com Change-Id: I98960f295987857c4e42c312059b6d5934bb5e43 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 109 Reviewed-on: https://boringssl-review.googlesource.com/24747 Reviewed-by: David Benjamin <firstname.lastname@example.org> Commit-Queue: 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: