commit | d477c0d7c40ddca3a64ae26fc02d2dac175836d3 | [log] [tgz] |
---|---|---|
author | Andres Erbsen <andreser@google.com> | Thu May 16 17:55:15 2024 +0000 |
committer | David Benjamin <davidben@google.com> | Thu May 16 21:00:48 2024 +0000 |
tree | 4741d4c4bc5b99c093aac7d9f08b2ed33f683d95 | |
parent | c70190368c7040c37c1d655f0690bcde2b109a0d [diff] |
use AT&T syntax in fiat_p256_adx Converted using https://github.com/andres-erbsen/fiat-crypto/commit/86a8bdcc1073fb55c01090ef8df622ea2c901ee1 Change-Id: Ic3b4f5b0f52a21eebd7c597a8caebf7b08c21fe3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/68527 Reviewed-by: Andres Erbsen <andreser@google.com> Reviewed-by: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: 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: