| commit | 621c9d45e731af5e7b4dc1fb40ffdec9ce541a18 | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Mon Jul 29 09:57:04 2019 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Jul 30 21:06:50 2019 +0000 |
| tree | 7321c05b432658770d3c6fe67f60626448ed982c | |
| parent | 9f6acfc1f29aa69755b7a9699eb3f6105cb5655c [diff] |
Move CCM fragments out of the FIPS module. In order to clarify that CCM is not a service offered by the FIPS module, move the CCM-related fragments of code out of the module to where they are used in the outer part of libcrypto. Change-Id: I64f95867a92fb90ea8bb460e2608c998669bb543 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/36804 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: