| commit | 043fba24112eddaa2d73c5bc36dc80014c8ef132 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Oct 21 11:14:59 2020 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Oct 22 13:15:29 2020 +0000 |
| tree | c32ec07f564f53a0d057cded57fa65be55cc4354 | |
| parent | e9fce74f2e88d74006d659eb079d4710eb017d86 [diff] |
Clear some reported gcc -Wshadow warnings. The constructor parameter vs. method name one is a little unfortunate given Google C++ style, but I think we've done this elsewhere in libssl, so let's run with it for now. Bug: 378 Change-Id: I31fb6b4b16e3248369dae6f47cc150de0e4f04fe Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/43545 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: 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.
Project links:
There are other files in this directory which might be helpful: