David Benjamin 3ab6ad6abd Simplify EC_KEY_set_public_key_affine_coordinates. EC_POINT_set_affine_coordinates_GFp already rejects coordinates which are out of range. There's no need to double-check. Change-Id: Id1685355c555dda66d2a14125cb0083342f37e53 Reviewed-on: https://boringssl-review.googlesource.com/24688 Reviewed-by: Adam Langley <agl@google.com>		vor 6 Jahren
.github	Add a PULL_REQUEST_TEMPLATE.	vor 8 Jahren
crypto	Simplify EC_KEY_set_public_key_affine_coordinates.	vor 6 Jahren
decrepit	Rename all googletest CMake targets	vor 6 Jahren
fipstools	Have run_cavp.go create “resp” directories as needed.	vor 7 Jahren
fuzz	Refresh fuzzer corpora.	vor 6 Jahren
include/openssl	Add a function for encoding SET OF.	vor 6 Jahren
infra/config	Revert "Add new bots to the CQ."	vor 7 Jahren
ssl	Map NOT_YET_VALID errors to \|certificate_expired\|.	vor 6 Jahren
third_party	Use fiat-crypto's freeze function for fe_tobytes.	vor 6 Jahren
tool	Remove deprecated TLS 1.3 variants.	vor 6 Jahren
util	Support delocating vpbroadcastq.	vor 6 Jahren
.clang-format	Import `newhope' (post-quantum key exchange).	vor 8 Jahren
.gitignore	Add sde-linux64 to .gitignore.	vor 7 Jahren
API-CONVENTIONS.md	Fix API-CONVENTIONS.md typos.	vor 7 Jahren
BUILDING.md	Document the NDK's built-in toolchain file.	vor 6 Jahren
CMakeLists.txt	Rename all googletest CMake targets	vor 6 Jahren
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	vor 8 Jahren
FUZZING.md	Fix typo in FUZZING.md.	vor 7 Jahren
INCORPORATING.md	Update links to Bazel's site.	vor 8 Jahren
LICENSE	curve25519: fiat-crypto field arithmetic.	vor 7 Jahren
PORTING.md	Switch OPENSSL_VERSION_NUMBER to 1.1.0.	vor 7 Jahren
README.md	Add an API-CONVENTIONS.md document.	vor 8 Jahren
STYLE.md	Fix some style guide samples.	vor 7 Jahren
codereview.settings	No-op change to trigger the new Bazel bot.	vor 8 Jahren
sources.cmake	Add a test for lots of names and constraints.	vor 7 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.
API-CONVENTIONS.md: general API conventions for BoringSSL consumers and developers.
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.