| commit | f03cdc3a936a4e4f00cd8fcf978ce195db3e717e | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jun 12 18:53:40 2017 -0400 |
| committer | David Benjamin <davidben@google.com> | Tue Jun 13 17:47:20 2017 +0000 |
| tree | 1bd3d2be0741d536b2ac7f102623bb7b3642743e | |
| parent | 8da59555c6d6f11c3f22f8c76f09b057786f657a [diff] |
Sync ARM assembly up to 609b0852e4d50251857dbbac3141ba042e35a9ae. This change was made by copying over the files as of that commit and then discarding the parts of the diff which corresponding to our own changes. Change-Id: I28c5d711f7a8cec30749b8174687434129af5209 Reviewed-on: https://boringssl-review.googlesource.com/17111 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: