| commit | e5fe31cfe734ca6d9fd1f1a84c48fe1c49f8e01b | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Mar 19 14:06:51 2021 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Mar 22 18:31:56 2021 +0000 |
| tree | 36e3f123723727b59981f930b60aa0c1dd7ad8c1 | |
| parent | 8c31179d81081cc9b8ce5b5ac3151088c45042f7 [diff] |
Revert "Implement rsa_pkcs1_sha256_legacy." This reverts commit a3437c09c77bab011d0bebb8f61a6df82eb53eec. There was a miscommunication and it does not seem like we currently need this. If that changes later, it's in Git and we can bring it back easily. Change-Id: Ibbce29df2258a2d893d725ab3ee6fd78c5b6cb00 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46286 Reviewed-by: Adam Langley <agl@google.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:
There are other files in this directory which might be helpful: