|author||Bob Haarman <email@example.com>||Fri Aug 09 14:13:58 2019 -0700|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Aug 09 22:05:17 2019 +0000|
Add missing ".text" to Windows code for dummy_chacha20_poly1305_asm This explicitly sets the section for the dummy_chacha20_poly1305_asm symbol we generate for Windows. Without explicitly setting the section, NASM would store it as an undefined symbol rather than a defined symbol, resulting in a broken object file. Change-Id: If8ff18f714be5e46af59ff869ae93e64e2c6e44b Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37024 Reviewed-by: David Benjamin <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.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: