commit | f466cdb5e0e2cd2a2edcfb02b031c47dacd9b297 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Mar 14 15:35:27 2017 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Sat Mar 25 21:59:49 2017 +0000 |
tree | 553c5dc2b2eb36d5d9ffb1d32921bc2083998407 | |
parent | bbf4246546a0869cad9459cb398781f1f4e356e3 [diff] |
size_t the RSA padding add functions. The padding check functions will need to tweak their calling conventions and the constant-time helpers, so leaving those alone for now. These were the easy ones. BUG=22 Change-Id: Ia00e41e26a134de17d56be3def5820cb042794e1 Reviewed-on: https://boringssl-review.googlesource.com/14265 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
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.
There are other files in this directory which might be helpful: