|author||David Benjamin <firstname.lastname@example.org>||Fri Nov 09 17:36:12 2018 -0600|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Tue Nov 13 17:27:59 2018 +0000|
Clean up EC_POINT to byte conversions. With the allocations and BN_CTX gone, ECDH and point2oct are much, much shorter. Bug: 242 Change-Id: I3421822e94100f7eb2f5f2373df7fb3b3311365e Reviewed-on: https://boringssl-review.googlesource.com/c/33071 Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> Reviewed-by: Adam Langley <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: