|author||David Benjamin <email@example.com>||Tue Jan 07 11:33:18 2020 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Jan 07 17:04:27 2020 +0000|
Clarify that we perform the point-on-curve check. Points not on the curve are invalid inputs to EC functions, so EC implementations should check the curve equation whenever importing points from the caller. Sadly, a number of implementations, including older OpenSSLs, miss this important check, so careful callers want this clarified in the documentation. Also update the note about OpenSSL to reflect the current behavior. While I'm here, const-correct EC_KEY_key2buf. Change-Id: I6fde5c823c4f3f6b141ba1566f427d96cd5881df Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39364 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: