Toshit Chawda 3b2e4b2ded fix for newer protobuf (it builds on arch again)		1 tahun lalu
..
.github	56b5d438ae clean up source tree	2 tahun lalu
cmake	56b5d438ae clean up source tree	2 tahun lalu
crypto	56b5d438ae clean up source tree	2 tahun lalu
decrepit	56b5d438ae clean up source tree	2 tahun lalu
fuzz	56b5d438ae clean up source tree	2 tahun lalu
include	56b5d438ae clean up source tree	2 tahun lalu
rust	56b5d438ae clean up source tree	2 tahun lalu
ssl	56b5d438ae clean up source tree	2 tahun lalu
third_party	56b5d438ae clean up source tree	2 tahun lalu
tool	56b5d438ae clean up source tree	2 tahun lalu
util	56b5d438ae clean up source tree	2 tahun lalu
.clang-format	56b5d438ae clean up source tree	2 tahun lalu
.gitignore	56b5d438ae clean up source tree	2 tahun lalu
API-CONVENTIONS.md	56b5d438ae clean up source tree	2 tahun lalu
BREAKING-CHANGES.md	56b5d438ae clean up source tree	2 tahun lalu
BUILDING.md	56b5d438ae clean up source tree	2 tahun lalu
CMakeLists.txt	3b2e4b2ded fix for newer protobuf (it builds on arch again)	1 tahun lalu
CONTRIBUTING.md	56b5d438ae clean up source tree	2 tahun lalu
FUZZING.md	56b5d438ae clean up source tree	2 tahun lalu
INCORPORATING.md	56b5d438ae clean up source tree	2 tahun lalu
LICENSE	56b5d438ae clean up source tree	2 tahun lalu
PORTING.md	56b5d438ae clean up source tree	2 tahun lalu
README.md	56b5d438ae clean up source tree	2 tahun lalu
SANDBOXING.md	56b5d438ae clean up source tree	2 tahun lalu
STYLE.md	56b5d438ae clean up source tree	2 tahun lalu
codereview.settings	56b5d438ae clean up source tree	2 tahun lalu
go.mod	56b5d438ae clean up source tree	2 tahun lalu
go.sum	56b5d438ae clean up source tree	2 tahun lalu
sources.cmake	56b5d438ae clean up source tree	2 tahun lalu

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.

Project links:

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.
BREAKING-CHANGES.md: notes on potentially-breaking changes.
SANDBOXING.md: notes on using BoringSSL in a sandboxed environment.

README.md

BoringSSL