Du kannst nicht mehr als 25 Themen auswählen Themen müssen entweder mit einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
 
 
 
 
 
 
David Benjamin ced9479fd1 Replace hash_current_message with get_current_message. vor 8 Jahren
.github Add a PULL_REQUEST_TEMPLATE. vor 8 Jahren
crypto Check for i2d_name_canon failures in x509_name_canon. vor 8 Jahren
decrepit Fix up macros. vor 8 Jahren
fuzz Add corpora for fuzzers with fuzzer mode disabled. vor 8 Jahren
include/openssl Move tlsext_ticket_expected to SSL_HANDSHAKE. vor 8 Jahren
infra/config Commit-Queue config: effectively remove Andorid builders. vor 8 Jahren
ssl Replace hash_current_message with get_current_message. vor 8 Jahren
third_party/android-cmake Move android-cmake README to METADATA file. vor 8 Jahren
tool Correctness fixes for NaCl and other platforms. vor 8 Jahren
util Fix Android bots. vor 8 Jahren
.clang-format Import `newhope' (post-quantum key exchange). vor 8 Jahren
.gitignore Fix documentation generation on Windows. vor 9 Jahren
API-CONVENTIONS.md Update API-CONVENTIONS.md for the new scopers. vor 8 Jahren
BUILDING.md Allow .arch directives with Clang. vor 8 Jahren
CMakeLists.txt Allow building on MIPS. vor 8 Jahren
CONTRIBUTING.md Add a CONTRIBUTING.md file. vor 8 Jahren
FUZZING.md Add corpora for fuzzers with fuzzer mode disabled. vor 8 Jahren
INCORPORATING.md Update links to Bazel's site. vor 8 Jahren
LICENSE Add some bug references to the LICENSE file. vor 8 Jahren
PORTING.md Add a note in PORTING to ask us before adding ifdefs. vor 8 Jahren
README.md Add an API-CONVENTIONS.md document. vor 8 Jahren
STYLE.md Clarify CBS/CBB with respect to high tag number form. vor 8 Jahren
codereview.settings No-op change to trigger the new Bazel bot. vor 8 Jahren

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: