|author||David Benjamin <firstname.lastname@example.org>||Tue Jan 19 15:36:43 2016 -0500|
|committer||Adam Langley <email@example.com>||Wed Jan 20 17:26:13 2016 +0000|
Drop the silly 'ECDH_' prefix on X25519. I got that from the TLS 1.3 draft, but it's kind of silly-looking. X25519 already refers to a Diffie-Hellman primitive. Also hopefully the WG will split NamedGroups and SignatureAlgorithms per the recent proposal, so it won't be needed anyway. (Most chatter is about what hashes should be allowed with what NIST curves, so it seems like people like the split itself? We'll see.) Change-Id: I7bb713190001199a3ebd30b67df2c00d29132431 Reviewed-on: https://boringssl-review.googlesource.com/6912 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: