commit | c18ef750ee7f6c5a6abdca8b7848286250784a06 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@chromium.org> | Fri Dec 18 22:42:51 2015 -0500 |
committer | Adam Langley <agl@google.com> | Tue Dec 22 18:56:53 2015 +0000 |
tree | 55080091980e3b66a3db7f01c0244b3690bda999 | |
parent | 3a2a48086b81077e11ca2819b03e1016598035d5 [diff] |
Allocate a NID for X25519. No corresponding OID, but SSL_CTX_set1_curves assumes NIDs exist. BUG=571231 Change-Id: Id5221cdc59132e26a89ae5f8978b946de690b4e0 Reviewed-on: https://boringssl-review.googlesource.com/6779 Reviewed-by: Adam Langley <agl@google.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: