| commit | d1c0de6fe0fe80f5004a8e6784c59b78829d21f1 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Mar 16 11:38:18 2017 -0400 |
| committer | Adam Langley <agl@google.com> | Thu Mar 30 15:38:43 2017 +0000 |
| tree | a1b709b7b399d2a6e9f29fdfa2c01f6715cafacf | |
| parent | f368c73826a96331e87e79f93be381a870ecc7c1 [diff] |
Add size_t variants of constant-time functions. These will be used in follow-up commits. The _s names are taken from upstream, to ease importing code. I've also promoted the CONSTTIME_* macros from the test. None of them are really necessary except ~0u cannot substitute for CONSTTIME_TRUE_S on 64-bit platforms, so having the macros seems safer. Once everything is converted, I expect the unsigned versions can be removed, so I've made the _8 and _int functions act on size_t rather than unsigned. The users of these functions basically only believe that array indices and bytes exist. BUG=22 Change-Id: I987bfb0c708dc726a6f2afcb05b6619bbd600564 Reviewed-on: https://boringssl-review.googlesource.com/14306 Commit-Queue: David Benjamin <davidben@google.com> 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: