|author||David Benjamin <firstname.lastname@example.org>||Wed Feb 14 19:50:38 2018 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Feb 15 01:42:54 2018 +0000|
Reject compressed ECDH coordinates in TLS. We don't advertise compressed coordinates (and point format negotiation was deprecated in TLS 1.3), so reject them. Both Internet Explorer and Firefox appear to reject them already. Later I hope to add an easier to use ECDH API that acts on bytes, not EC_POINT. This clears the way for that API to only accept uncompressed coordinates. Compressed coordinates never got deployed over NIST curves, for better or worse. At this point, there is no sense in changing that as new protocols should use curve25519. Change-Id: Id2f1be791ddcf155d596f4eb0b79351766c5cdab Reviewed-on: https://boringssl-review.googlesource.com/26024 Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <email@example.com> 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: