You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
David Benjamin 3d458dc048 Revert of Determining certificate_auth and key_exchange based on SSL. 8 vuotta sitten
.github Add a PULL_REQUEST_TEMPLATE. 8 vuotta sitten
crypto Use C99 for size_t loops. 8 vuotta sitten
decrepit Make OBJ_NAME_do_all more OpenSSL-compatible. 8 vuotta sitten
fuzz Update fuzzing corpus for ‘server’ 8 vuotta sitten
include/openssl Only allow SSL_set_session before the handshake. 8 vuotta sitten
infra/config Commit-Queue config: effectively remove Andorid builders. 8 vuotta sitten
ssl Revert of Determining certificate_auth and key_exchange based on SSL. 8 vuotta sitten
third_party/android-cmake Check in a copy of android-cmake. 8 vuotta sitten
tool Fix IWYU violation in speed.cc. 8 vuotta sitten
util Build debug symbols for assembly. 8 vuotta sitten
.clang-format Import `newhope' (post-quantum key exchange). 8 vuotta sitten
.gitignore Fix documentation generation on Windows. 9 vuotta sitten
API-CONVENTIONS.md Replace Scoped* heap types with bssl::UniquePtr. 8 vuotta sitten
BUILDING.md Allow .arch directives with Clang. 8 vuotta sitten
CMakeLists.txt Build debug symbols for assembly. 8 vuotta sitten
CONTRIBUTING.md Add a CONTRIBUTING.md file. 8 vuotta sitten
FUZZING.md Replace base64 decoding. 8 vuotta sitten
INCORPORATING.md Remove backslash. 8 vuotta sitten
LICENSE Add some bug references to the LICENSE file. 8 vuotta sitten
PORTING.md Add a note in PORTING to ask us before adding ifdefs. 8 vuotta sitten
README.md Add an API-CONVENTIONS.md document. 8 vuotta sitten
STYLE.md Clarify CBS/CBB with respect to high tag number form. 8 vuotta sitten
codereview.settings No-op change to trigger the new Bazel bot. 8 vuotta sitten

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: