Não pode escolher mais do que 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
 
 
 
 
 
 
David Benjamin 768e6822cc Only fixup CMAKE_ASM_FLAGS -isysroot if CMAKE_OSX_SYSROOT is set. há 7 anos
.github Add a PULL_REQUEST_TEMPLATE. há 8 anos
crypto Only fixup CMAKE_ASM_FLAGS -isysroot if CMAKE_OSX_SYSROOT is set. há 7 anos
decrepit Move des/ to crypto/fipsmodule/ há 7 anos
fipsoracle fipsoracle: Remove fax sample verification baked into test suites. This is covered by run_cavp.go. há 7 anos
fuzz Refresh fuzzer corpus. há 7 anos
include/openssl Add a flag to toggle the buggy RSA parser. há 7 anos
infra/config Restore ios64_compile to the CQ. há 7 anos
ssl Improve TestConfig flags for initial and resumption connections. há 7 anos
third_party Clear the last GTest warning suppression. há 7 anos
tool Make -loop survive errors. há 7 anos
util Add hash of SDE tool for the bots. há 7 anos
.clang-format Import `newhope' (post-quantum key exchange). há 8 anos
.gitignore Add an option to build libFuzzer from DEPS. há 7 anos
API-CONVENTIONS.md Fix API-CONVENTIONS.md typos. há 7 anos
BUILDING.md Add the start of standalone iOS build support. há 7 anos
CMakeLists.txt Fixing assembly coverage reporting. há 7 anos
CONTRIBUTING.md Add a CONTRIBUTING.md file. há 8 anos
FUZZING.md Fix FUZZING.md typo. há 7 anos
INCORPORATING.md Update links to Bazel's site. há 8 anos
LICENSE Add some bug references to the LICENSE file. há 8 anos
PORTING.md Restore SSL_CTX_set_ecdh_auto compatibility hook. há 7 anos
README.md Add an API-CONVENTIONS.md document. há 8 anos
STYLE.md Work around language and compiler bug in memcpy, etc. há 7 anos
codereview.settings No-op change to trigger the new Bazel bot. há 8 anos

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: