|author||Adam Langley <firstname.lastname@example.org>||Wed Oct 16 09:56:38 2019 -0700|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Oct 17 21:38:38 2019 +0000|
Add test for urandom.c This change adds a test to try and prevent errors like b8f760191e. Since it's challenging to test this code, it uses ptrace to capture a trace of the PRNG behaviour and checks that the observed behaviour matches a much smaller model of the code. The model is hopefully easier to read and believe correct. Change-Id: I00b811dc5692e2fbe3dcc16c622d4eb706f16ce0 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38265 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: David Benjamin <firstname.lastname@example.org>
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: