| commit | 64a8659b89dda348cdadcbec0f23d829ee6fd32d | [log] [tgz] |
|---|---|---|
| author | Adam Langley <agl@google.com> | Wed Nov 30 14:53:50 2016 -0800 |
| committer | Adam Langley <agl@google.com> | Mon Dec 05 21:37:16 2016 +0000 |
| tree | 026003226201c9a17d64c52559e3dd6d1dbcd377 | |
| parent | 48891ad07ca92aefa4fa41a5d21d317ad7f85b49 [diff] |
Rename BSWAP[48] to CRYPTO_bswap[48] and always define them. Previously, gcm.c contained a lot of workarounds for cases where BSWAP8 wasn't defined. Rather than handle this in each place, just make it always available. While we're here, make these macros inline functions instead and rename them to something less likely to collide. Change-Id: I9f2602f8b9965c63a86b177a8a084afb8b53a253 Reviewed-on: https://boringssl-review.googlesource.com/12479 Commit-Queue: Adam Langley <alangley@gmail.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: