commit | 147f1c468c937e0d05c9d1168f709c316a0697d2 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Sun Aug 28 02:22:46 2016 -0400 |
committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Aug 30 15:32:31 2016 +0000 |
tree | 12a307ef133ea95ccf255b33af34e4bf7532f3df | |
parent | 8c2d53ad990d4972b03b2048e87d0f190523d59c [diff] |
Simplify RC4 code and remove assembly. This removes all but the generic C RC4 implementation. At this point we want to optimize for size/simplicity rather than speed. See also upstream's 3e9e810f2e047effb1056211794d2d12ec2b04e7 which removed the RC4_CHUNK code and standardized on RC4_INDEX. A since-removed comment says that it was implemented for "pre-21164a Alpha CPUs don't have byte load/store instructions" and helps with SPARC and MIPS. This also removes all the manual loop unrolling. Change-Id: I91135568483260b2e1e675f190fb00ce8f9eff3d Reviewed-on: https://boringssl-review.googlesource.com/10720 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: