| commit | 1eea82a92a141416b3f0ee4d52434252cb948b47 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@imperialviolet.org> | Mon Oct 17 21:15:16 2022 +0000 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 18 02:43:21 2022 +0000 |
| tree | 47963eecc6461c457a322c26f6cc8116b4aac672 | |
| parent | 14aa0de18f638a92be13597bc1b8a95ca8fcf8a4 [diff] |
Break FIPS tests by zeroing out the entire value. Previously the code just flipped one bit. But, empirically, modern Clang will sometimes produce code that doesn't depend on the first 16 bytes of the data; they are encoded in the instructions instead. Thus zero out the full value. (If Clang ever starts embedding complete values into the instruction stream then we're going to have to do something more complex. Self tests are a bit funny: the compiler could reasonably optimise them away completely given that it sees all the inputs. Perhaps the inputs would have to be moved into a different object file.) Change-Id: I7bfb18cb7868def67fc791dcc31c5915c7728ac4 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54825 Commit-Queue: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> Auto-Submit: Adam Langley <agl@google.com> Reviewed-by: David Benjamin <davidben@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: