commit | ddd5ba78a949c5458aad9f7c3f19d214a2e8338e | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Tue Apr 11 12:54:06 2017 -0400 |
committer | Adam Langley <agl@google.com> | Wed Apr 12 22:06:11 2017 +0000 |
tree | d3b8a9d15cdcd7bb4b8add69e3df4e19ba54819c | |
parent | f004aa556d90648f31859e48c0052b62d78fed6d [diff] |
Remove redundant check in RSA_sign. This is just some idle cleanup. The padding functions already must handle size checks. Swap out the error code in the low-level portions to keep that unchanged. Also remove an old TODO(fork) about constant-time-ness. Signature verification padding checks don't need to be constant time, and decryption ones should be resolved now. Change-Id: I20e7affdb7f2dce167a304afe707bfd537dd412a Reviewed-on: https://boringssl-review.googlesource.com/14946 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.
There are other files in this directory which might be helpful: