commit | f3bfab0035fe671889250c1cc52973109bfc104f | [log] [tgz] |
---|---|---|
author | Ryan Tseng <hinoka@google.com> | Wed Jul 25 17:21:46 2018 -0700 |
committer | Ryan Tseng <hinoka@google.com> | Thu Jul 26 00:23:04 2018 +0000 |
tree | 602be373e853c48b8c2f61703b6600364ae4bf75 | |
parent | ed09f2d5cd2914820343b51caf1420bee2835e02 [diff] |
Comment change in codereview.settings gcl is long deprecated, "git cl" is what this is used for now. TBR: davidben Change-Id: I5980b8ff3a7c384f4650e195eb6e4daf52da5ae2 Reviewed-on: https://boringssl-review.googlesource.com/30064 Reviewed-by: Ryan Tseng <hinoka@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: