| commit | 1a541d4db65dddeb4996030bd196ac856c51c102 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Wed May 04 14:42:30 2022 -0700 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 05 14:34:17 2022 +0000 |
| tree | 4f3e72ae56d718f8bbbea5d15c8e80442e30f177 | |
| parent | 82413455b8cac53334bee770ffbaddaac6b95d34 [diff] |
Add PSS to the AVCP regcap. PSS verification with RSA 1024 is still acceptable. This change adds it to our regcap. SHA-512 is omitted because that doesn't fit in 1024 bits with PSS encoding. (Unless you shrink the salt, but we don't want to deal with odd PSS configurations like that.) Change-Id: I05d4778d45c25c87e2e50cd095380ecd4f12c75c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/52427 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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: