Revert "Replace most of P-256 assembly code with C" This reverts commit ba76be9c75d35798a397a8f6d741cc360a3026ae. This seems to have caused significant performance regressions in some configurations. See b/525050645 (internal). It was not a clean revert due to other changes that went in in the meantime. I had to revert the following other CLs: * 85a291c0ef3cd5774d961a39b286d253efe401b2 * 28950bf42fdaa937e31ee0be8e02e97bbc6a17dc * 6bec274e2a2d7dfc6ac3919d55264597695cb1c7 * 66370b6b9301fdf4d316d049581832cba46a4e99 Then I resolved merge conflicts with the changes to put a symbol at the start of all the .rodata sections, and then reapplied 28950bf42fdaa937e31ee0be8e02e97bbc6a17dc and 6bec274e2a2d7dfc6ac3919d55264597695cb1c7, but to where the code used to be. I also kept the changes to: - crypto/ecdh/ecdh_test.cc - crypto/internal.h - third_party/fiat/bedrock_unverified_platform.c.inc Bug: 525050645 Change-Id: I1a016785dfa3da57ac07d26dd034a67d0bc14566 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/97607 Reviewed-by: Adam Langley <agl@google.com> Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Commit-Queue: David Benjamin <davidben@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.
Project links:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: