No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.
 
 
 
 
 
 
Adam Langley 4c341d0299 Support asynchronous ticket decryption with TLS 1.0–1.2. hace 7 años
.github Add a PULL_REQUEST_TEMPLATE. hace 8 años
crypto Support asynchronous ticket decryption with TLS 1.0–1.2. hace 7 años
decrepit Move the SSL BIO into ssl/ from decrepit/. hace 7 años
fuzz Remove experimental TLS 1.3 short record header extension. hace 7 años
include/openssl Support asynchronous ticket decryption with TLS 1.0–1.2. hace 7 años
infra/config Commit-Queue config: effectively remove Andorid builders. hace 8 años
ssl Support asynchronous ticket decryption with TLS 1.0–1.2. hace 7 años
third_party Clear the last GTest warning suppression. hace 7 años
tool Don't pass |overhead_len| when testing “open” speed. hace 7 años
util Sync util/bot with Chromium. hace 7 años
.clang-format Import `newhope' (post-quantum key exchange). hace 8 años
.gitignore Also add util/bot/golang to .gitignore. hace 8 años
API-CONVENTIONS.md Fix API-CONVENTIONS.md typos. hace 7 años
BUILDING.md Do a cursory conversion of a few tests to GTest. hace 7 años
CMakeLists.txt Build with -fsanitize-address-use-after-scope if -DASAN=1 hace 7 años
CONTRIBUTING.md Add a CONTRIBUTING.md file. hace 8 años
FUZZING.md Merge in upstream's certificate corpus. hace 7 años
INCORPORATING.md Update links to Bazel's site. hace 8 años
LICENSE Add some bug references to the LICENSE file. hace 8 años
PORTING.md Add a note in PORTING to ask us before adding ifdefs. hace 8 años
README.md Add an API-CONVENTIONS.md document. hace 8 años
STYLE.md Work around language and compiler bug in memcpy, etc. hace 7 años
codereview.settings No-op change to trigger the new Bazel bot. hace 8 años

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: