| commit | 47b1e39042bc3208771a8d947f1a1ed2fe5f3d8b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Apr 23 11:51:56 2020 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Thu Apr 23 19:50:07 2020 +0000 |
| tree | 809e7ab6522c3243b634663d350f4af70f6ff0f5 | |
| parent | 25ab623a86be1e202771f197846a6e4e8aca3520 [diff] |
Tidy up third_party/fiat. Originally, when we imported fiat-crypto field operations, the pipeline was in early stages and the generated code had to be manually integrated with the rest of the curve implementation, so we moved all our supporting code to third_party/fiat for simplicity. Over time more supporting code, like the table generators, landed there to be next to its callers. fiat-crypto now generates standalone files which we #include into the supporting code. This moves the supporting code back to the usual location. It also updates the README.md file to reflect the new pipeline. (Most of it was a documentation of the old pipeline, which was much more manual.) Change-Id: I64db7235feb6566f0d3cd4db3a7146050edaf25a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/40904 Commit-Queue: David Benjamin <davidben@google.com> 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.
Project links:
There are other files in this directory which might be helpful: