David Benjamin 6fdea2aba9 Move PKCS#7 functions into their own directory. A follow-up change will add a CRYPTO_BUFFER variant. This makes the naming match the header and doesn't require including x509.h. (Though like ssl.h and pkcs8.h, some of the functions are implemented with code that depends on crypto/x509.) Change-Id: I5a7de209f4f775fe0027893f711326d89699ca1f Reviewed-on: https://boringssl-review.googlesource.com/15128 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>		7 år sedan
.github	Add a PULL_REQUEST_TEMPLATE.	8 år sedan
crypto	Move PKCS#7 functions into their own directory.	7 år sedan
decrepit	First part of the FIPS module.	7 år sedan
fuzz	Add SSL_CTX_set_verify_algorithm_prefs.	7 år sedan
include/openssl	Move PKCS#7 functions into their own directory.	7 år sedan
infra/config	Add linux_fips_noasm_asan.	7 år sedan
ssl	Enforce max_early_data_size on the server.	7 år sedan
third_party	Clear the last GTest warning suppression.	7 år sedan
tool	Make -loop survive errors.	7 år sedan
util	Move PKCS#7 functions into their own directory.	7 år sedan
.clang-format	Import `newhope' (post-quantum key exchange).	8 år sedan
.gitignore	Also add util/bot/golang to .gitignore.	8 år sedan
API-CONVENTIONS.md	Fix API-CONVENTIONS.md typos.	7 år sedan
BUILDING.md	Add the start of standalone iOS build support.	7 år sedan
CMakeLists.txt	Add the start of standalone iOS build support.	7 år sedan
CONTRIBUTING.md	Add a CONTRIBUTING.md file.	8 år sedan
FUZZING.md	Fix FUZZING.md typo.	7 år sedan
INCORPORATING.md	Update links to Bazel's site.	8 år sedan
LICENSE	Add some bug references to the LICENSE file.	8 år sedan
PORTING.md	Restore SSL_CTX_set_ecdh_auto compatibility hook.	7 år sedan
README.md	Add an API-CONVENTIONS.md document.	8 år sedan
STYLE.md	Work around language and compiler bug in memcpy, etc.	7 år sedan
codereview.settings	No-op change to trigger the new Bazel bot.	8 år sedan

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.