|author||David Benjamin <email@example.com>||Sat May 04 14:25:41 2019 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Mon May 06 23:23:18 2019 +0000|
Make expect/expected flag and variable names match. At one point we had -expect-foo and TestConfig::expect_foo for boolean flags and -expect-bar and TestConfig::expected_bar for flags that take a value. This seems to have been confusing and got applied inconsistently. Match the variable names to the flag names and consistently use "expect". Change-Id: Ia346b91ad37b1177918c50392f9f80a384926e27 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35889 Commit-Queue: David Benjamin <firstname.lastname@example.org> Reviewed-by: Adam Langley <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: