Steven Valdez 025638597a Changing representation of signature/hash to use SignatureScheme. As part of the SignatureAlgorithm change in the TLS 1.3 specification, the existing signature/hash combinations are replaced with a combined signature algorithm identifier. This change maintains the existing APIs while fixing the internal representations. The signing code currently still treats the SignatureAlgorithm as a decomposed value, which will be fixed as part of a separate CL. Change-Id: I0cd1660d74ad9bcf55ce5da4449bf2922660be36 Reviewed-on: https://boringssl-review.googlesource.com/8480 Reviewed-by: Steven Valdez <svaldez@google.com> Reviewed-by: David Benjamin <davidben@google.com>		vor 8 Jahren
.github	Add a PULL_REQUEST_TEMPLATE.	vor 8 Jahren
crypto	Move more non-bc tests down.	vor 8 Jahren
decrepit	Make OBJ_NAME_do_all more OpenSSL-compatible.	vor 8 Jahren
fuzz	Replace base64 decoding.	vor 8 Jahren
include/openssl	Changing representation of signature/hash to use SignatureScheme.	vor 8 Jahren
ssl	Changing representation of signature/hash to use SignatureScheme.	vor 8 Jahren
third_party/android-cmake	Check in a copy of android-cmake.	vor 8 Jahren
tool	Handle IPv6 literals in bssl client.	vor 8 Jahren
util	Convert test_add and test_sub to file_test.	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	Document compiler and assembler requirements.	vor 8 Jahren
CMakeLists.txt	Spell C++11 as C++11, not C++0x.	vor 8 Jahren
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
FUZZING.md	Replace base64 decoding.	vor 8 Jahren
INCORPORATING.md	Update INCORPORATING.md to clarify one point.	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 document about incorporating BoringSSL into a project.	vor 8 Jahren
STYLE.md	Update style guide note on files which match OpenSSL.	vor 8 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
INCORPORATING.md: how to incorporate BoringSSL into a project.
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.