commit | 4ec0cce743d0aaa2f10ad6cd17c7e4f6d4f5ff4c | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@chromium.org> | Fri Dec 11 15:31:07 2015 -0500 |
committer | Adam Langley <agl@google.com> | Wed Dec 16 21:19:32 2015 +0000 |
tree | cd2d4c0150036a5c9a2e3ef3e4fc8c4df6888d76 | |
parent | 2936170d68ec617e1e6f0c2def86728ba29312b7 [diff] |
Slightly tweak some array allocations. clang scan-build is annoyed it's not obvious the sizeof line matches the pointer type. This is easy to fix and makes it be quiet. Change-Id: Iec80d2a087f81179c88cae300f56d3f76b32b347 Reviewed-on: https://boringssl-review.googlesource.com/6701 Reviewed-by: Adam Langley <agl@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: