Matt Braithwaite 045a0ffe35 Import `newhope' (post-quantum key exchange). This derives from the reference implementation: Source: https://github.com/tpoeppelmann/newhope/tree/master/ref at bc06c1ac Paper: https://eprint.iacr.org/2015/1092 However, it does not interoperate, due to the replacement of SHAKE-128 with AES-CTR (for polynomial generation) and the replacement of SHA-3 with SHA-256 (for key whitening). Change-Id: I6a55507aea85331245e2fbd41bae5cc049fdca3c Reviewed-on: https://boringssl-review.googlesource.com/7690 Reviewed-by: Adam Langley <agl@google.com>		vor 8 Jahren
.github	Add a PULL_REQUEST_TEMPLATE.	vor 8 Jahren
crypto	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
decrepit	Export RSA_padding_add_PKCS1_OAEP[_mgf1]	vor 8 Jahren
fuzz	Add standalone PKCS#8 and SPKI fuzzers.	vor 8 Jahren
include/openssl	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
ssl	Ensure we check i2d_X509 return val	vor 8 Jahren
tool	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
util	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
.clang-format	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
.gitignore	Fix documentation generation on Windows.	vor 9 Jahren
BUILDING.md	Enable upstream's ChaCha20 assembly for x86 and ARM (32- and 64-bit).	vor 8 Jahren
CMakeLists.txt	Fix build when using Visual Studio 2015 Update 1.	vor 8 Jahren
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
FUZZING.md	Add standalone PKCS#8 and SPKI fuzzers.	vor 8 Jahren
LICENSE	Add some bug references to the LICENSE file.	vor 8 Jahren
PORTING.md	Document the d2i object reuse changes in PORTING.md.	vor 8 Jahren
README.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
STYLE.md	Update link to Google style guide.	vor 9 Jahren
codereview.settings	Add a codereview.settings file.	vor 10 Jahren

README.md

BoringSSL

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:

PORTING.md: how to port OpenSSL-using code to BoringSSL.
BUILDING.md: how to build BoringSSL
STYLE.md: rules and guidelines for coding style.
include/openssl: public headers with API documentation in comments. Also available online.
FUZZING.md: information about fuzzing BoringSSL.
CONTRIBUTING.md: how to contribute to BoringSSL.