Vous ne pouvez pas sélectionner plus de 25 sujets Les noms de sujets doivent commencer par une lettre ou un nombre, peuvent contenir des tirets ('-') et peuvent comporter jusqu'à 35 caractères.
 
 
 
 
 
 
David Benjamin 30152fdfc1 Always buffer DTLS retransmits. il y a 8 ans
.github Add a PULL_REQUEST_TEMPLATE. il y a 8 ans
crypto Do RSA blinding unless |e| is NULL and specifically requested not to. il y a 8 ans
decrepit Revert md_len removal from SHA256_CTX and SHA512_CTX. il y a 8 ans
fuzz Add standalone PKCS#8 and SPKI fuzzers. il y a 8 ans
include/openssl Add BORINGSSL_API_VERSION. il y a 8 ans
ssl Always buffer DTLS retransmits. il y a 8 ans
tool Pass array by reference in newhope speed test. il y a 8 ans
util Fix vs_toolchain.py, possibly. il y a 8 ans
.clang-format Import `newhope' (post-quantum key exchange). il y a 8 ans
.gitignore Fix documentation generation on Windows. il y a 9 ans
BUILDING.md Bump requirements to MSVC 2015. il y a 8 ans
CMakeLists.txt Start assuming MSVC 2015. il y a 8 ans
CONTRIBUTING.md Add a CONTRIBUTING.md file. il y a 8 ans
FUZZING.md Add standalone PKCS#8 and SPKI fuzzers. il y a 8 ans
INCORPORATING.md Correct markdown misinterpretation. il y a 8 ans
LICENSE Add some bug references to the LICENSE file. il y a 8 ans
PORTING.md Document the d2i object reuse changes in PORTING.md. il y a 8 ans
README.md Add document about incorporating BoringSSL into a project. il y a 8 ans
STYLE.md Update link to Google style guide. il y a 9 ans
codereview.settings Add a codereview.settings file. il y a 10 ans

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: