kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
3,928 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
c90ed1901d
Go to file
David Benjamin c90ed1901d Tidy up error-handling around computing the hash in PSS. 
EVP_DigestUpdate can tolerate zero length inputs. Also properly clean up
ctx in all codepaths.

Change-Id: I90889c6236f6bf74625ba9f967de36949a9a6f83
Reviewed-on: https://boringssl-review.googlesource.com/14327
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Steven Valdez <svaldez@google.com>
Reviewed-by: Steven Valdez <svaldez@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-23 15:07:08 +00:00
.github
crypto Tidy up error-handling around computing the hash in PSS. 2017-03-23 15:07:08 +00:00
decrepit Convert bio_test to GTest. 2017-03-21 17:39:57 +00:00
fuzz Remove experimental TLS 1.3 short record header extension. 2017-03-02 22:39:17 +00:00
include/openssl Name |select_certificate_cb| return values 2017-03-22 01:27:00 +00:00
infra/config
ssl Name |select_certificate_cb| return values 2017-03-22 01:27:00 +00:00
third_party Clear the last GTest warning suppression. 2017-02-16 19:03:32 +00:00
tool tool: fix typo in -root-certs description 2017-03-20 17:39:42 +00:00
util Convert bio_test to GTest. 2017-03-21 17:39:57 +00:00
.clang-format
.gitignore
API-CONVENTIONS.md
BUILDING.md Do a cursory conversion of a few tests to GTest. 2017-01-21 00:17:05 +00:00
CMakeLists.txt Build with -fsanitize-address-use-after-scope if -DASAN=1 2017-02-28 20:07:09 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md
INCORPORATING.md
LICENSE
PORTING.md Restore SSL_CTX_set_ecdh_auto compatibility hook. 2017-03-14 14:54:45 +00:00
README.md
STYLE.md Work around language and compiler bug in memcpy, etc. 2016-12-21 20:34:47 +00:00

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: