| commit | 17ce286e0792fc2855fb7e34a968bed17ae914af | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Jun 07 15:30:11 2017 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Jun 07 19:59:24 2017 +0000 |
| tree | fa38df1870822d3b7fbf0332cd0da4bf817cd831 | |
| parent | d91e1efd835f84b2b59467ae78ace3b516730344 [diff] |
Work around an apparent Linux or glibc bug on ppc64le in FIPS mode. POWER8 has hardware transactional memory, which glibc uses to implement locks. In some cases, taking a lock begins a transaction, wrapping arbitrary user code (!) until the lock is released. If the transaction is aborted, everything rewinds and glibc tries again with some other implementation. The kernel will abort the transaction in a variety of cases. Notably, on a syscall, the transaction aborts and the syscall *does not happen*. https://www.kernel.org/doc/Documentation/powerpc/transactional_memory.txt Yet, for some reason, although the relevant change does appear to be in the kernel, the transaction is being rewound with getrandom happening anyway. This does not work very well. Instead, only guard the DRBG access with the lock, not CRYPTO_sysrand. This lock is only used to protect the DRBG from the destructor that zeros everything. Change-Id: Ied8350f1e808a09300651de4200c7b0d07b3a158 Reviewed-on: https://boringssl-review.googlesource.com/16985 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@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: