|author||David Benjamin <firstname.lastname@example.org>||Thu Nov 02 20:44:26 2017 -0400|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Fri Nov 03 01:32:49 2017 +0000|
Support additional curve names. Node's default settings spell P-256 as prime256v1. This comes from OpenSSL additionally allowing the long and short names of each curve's NID. This works out to one additional name per curve for the ones we support. To avoid depending on the giant OID table, this replicates the names in libssl. Change-Id: I456a2db6939eb6745e5a9d2f12cf6886e6265b9f Reviewed-on: https://boringssl-review.googlesource.com/22545 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <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: