| commit | bf3335c62143b1d1b847cb5bea24b70e7c6407b0 | [log] [tgz] |
|---|---|---|
| author | William Hesse <whesse@google.com> | Tue Feb 02 15:31:53 2016 +0100 |
| committer | Adam Langley <agl@google.com> | Tue Feb 02 16:03:33 2016 +0000 |
| tree | 85242cf7d47c5bfa6349cba66adfa81863c3e28f | |
| parent | 72f7e21087aaf38c781de3e659ccf13f0735de27 [diff] |
Add #ifdef guards to crypto/curve25519 assembly files. Add guards for the architecture and OPENSSL_NO_ASM to the assembly-language files in crypto/curve25519/asm. The Dart compilation of BoringSSL includes all files, because the architecture is not known when gyp is run. Change-Id: I66f5ae525266b63b0fe3a929012b771d545779b5 Reviewed-on: https://boringssl-review.googlesource.com/7030 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: