Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 
 
 
 
 
Adam Langley d515722d22 Don't depend on the X509 code for getting public keys. pirms 7 gadiem
.github Add a PULL_REQUEST_TEMPLATE. pirms 8 gadiem
crypto Don't depend on the X509 code for getting public keys. pirms 7 gadiem
decrepit Remove unused BIO_RR_* values. pirms 7 gadiem
fuzz Merge in upstream's certificate corpus. pirms 7 gadiem
include/openssl Don't depend on the X509 code for getting public keys. pirms 7 gadiem
infra/config Commit-Queue config: effectively remove Andorid builders. pirms 8 gadiem
ssl Don't depend on the X509 code for getting public keys. pirms 7 gadiem
third_party/android-cmake Move android-cmake README to METADATA file. pirms 8 gadiem
tool tool: show if server sent OCSP staple pirms 7 gadiem
util Remove New Hope key agreement. pirms 7 gadiem
.clang-format Import `newhope' (post-quantum key exchange). pirms 8 gadiem
.gitignore Also add util/bot/golang to .gitignore. pirms 8 gadiem
API-CONVENTIONS.md Update API-CONVENTIONS.md for the new scopers. pirms 8 gadiem
BUILDING.md Allow .arch directives with Clang. pirms 8 gadiem
CMakeLists.txt Add ppc64le vector implementation of SHA-1. pirms 8 gadiem
CONTRIBUTING.md Add a CONTRIBUTING.md file. pirms 8 gadiem
FUZZING.md Merge in upstream's certificate corpus. pirms 7 gadiem
INCORPORATING.md Update links to Bazel's site. pirms 8 gadiem
LICENSE Add some bug references to the LICENSE file. pirms 8 gadiem
PORTING.md Add a note in PORTING to ask us before adding ifdefs. pirms 8 gadiem
README.md Add an API-CONVENTIONS.md document. pirms 8 gadiem
STYLE.md Clarify CBS/CBB with respect to high tag number form. pirms 8 gadiem
codereview.settings No-op change to trigger the new Bazel bot. pirms 8 gadiem

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: