|author||David Benjamin <firstname.lastname@example.org>||Tue Jul 07 17:56:05 2020 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Wed Jul 29 19:27:59 2020 +0000|
Use golang.org/x/crypto in runner. The CI should be set up to retain the Go module and build caches, so we'll avoid downloading it multiple times. This avoids having to replicate some code. Update-Note: The tests now have a golang.org/x/crypto dependency. This should be fetched transparently with Go modules. Monorepos with different import path conventions may need to rewrite these imports. Change-Id: If5ba52e051f180536d72109c2e690bbd13d58e7c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/42044 Reviewed-by: Adam Langley <email@example.com> Commit-Queue: 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: