|author||David Benjamin <email@example.com>||Wed Jan 22 16:52:53 2020 -0500|
|committer||Adam Langley <firstname.lastname@example.org>||Wed Jan 22 23:03:16 2020 +0000|
Define EVP compatibility constants for X448 and Ed448. We do not support these, but Node expects the constants to be there, so define them. Also fill in X25519's OID. Now that we can wrap it in EVP_PKEY, we should have the OID there. (Our serializers don't use the giant OID table, which is why it didn't matter.) Change-Id: Ie0637f0e525c5704a9354c743075c027ace2f631 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39724 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: