|author||David Benjamin <email@example.com>||Sat Sep 14 21:43:04 2019 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Mon Sep 16 16:55:31 2019 +0000|
Parse explicit EC curves more strictly. Wycheproof has a series of ECDH tests for whether we reject misspelled explicit versions of named curves in public keys, including the wrong cofactor. We pass those tests easily because we reject those in public keys altogether, consistent with RFC 5480. However, we do parse explicit curves for private keys, for compatibility with keys produced by older OpenSSLs with unfortunate defaults. Were that parser enabled for public keys too, we would trip some of these Wycheproof tests because we ignore the cofactor. Tighten the parser up. If the cofactor is not one, ignore the curve. Also syntax-check the seed, even though we ignore it. Change-Id: I39936e027a72d2dc5532beb2407575ad8042d4c9 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37484 Commit-Queue: Adam Langley <firstname.lastname@example.org> 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: