| commit | 414f69504d30d0848b69f6453ea7fb5e88004cb4 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@chromium.org> | Thu Jan 18 13:47:20 2024 -0800 |
| committer | Adam Langley <agl@google.com> | Fri Jan 19 18:25:45 2024 +0000 |
| tree | 388be1495a70cb2f816f105be945286af9b3f9b4 | |
| parent | a32596b0545d2f6192a6a1be2f8e2c7c4f0c8f44 [diff] |
Reworking bssl_crypto: don't use zero keys in examples. Someone _probably_ wouldn't copy–paste an example to the point of using a zero key but, just in case, since we have `rand_array` now, we might as well use it so that the examples are safe. Change-Id: I289cb8f27894e8f0429fbbed37a1db3ea4295ffd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65567 Reviewed-by: Bob Beck <bbe@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: