| commit | 1607f54fed72c6589d560254626909a64124f091 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <alangley@gmail.com> | Tue Nov 03 15:34:57 2020 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Nov 04 22:04:09 2020 +0000 |
| tree | 0310f724e77400636db71ae57230cae30a240c64 | |
| parent | 17e530c43c70967c31b511329aa26220866ffe46 [diff] |
acvp: move inner MCT loops into subprocess. The ACVP MCT tests involve a double loop where the inner loop iterates 1000 (AES) or 10000 (3DES) times. This change moves that inner loop into the subprocess. This significantly reduces the amount of IPC traffic at the cost of making the subprocesses more complex. The traffic volume is unimportant when talking over a local pipe, but it's significant when channels like serial links are used. Change-Id: Ia9d51335f06b743791f7885d366c8fd2f0f7eaf6 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/43844 Commit-Queue: Adam Langley <alangley@gmail.com> Commit-Queue: 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: