kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4,178 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
e34eaa6409
Go to file
David Benjamin e34eaa6409 Remove old masm workaround. 
This dates to ded93581f1, but we have
since switched to building with nasm, to match upstream's supported
assemblers. Since this doesn't affect anything we generate, remove the
workaround to reduce the diff against upstream.

Change-Id: I549ae97ad6d6f28836f6c9d54dcf51c518de7521
Reviewed-on: https://boringssl-review.googlesource.com/15986
Reviewed-by: Adam Langley <agl@google.com>
2017-05-05 23:07:47 +00:00
.github
crypto Remove old masm workaround. 2017-05-05 23:07:47 +00:00
decrepit Move des/ to crypto/fipsmodule/ 2017-05-02 19:21:02 +00:00
fipsoracle fipsoracle: Remove fax sample verification baked into test suites. This is covered by run_cavp.go. 2017-05-04 22:10:37 +00:00
fuzz Add SSL_CTX_set_verify_algorithm_prefs. 2017-04-14 21:40:24 +00:00
include/openssl Add EVP_AEAD_CTX_[new|free] and UniquePtr support. 2017-05-05 21:29:44 +00:00
infra/config Add linux_fips_noasm_asan. 2017-04-18 19:27:05 +00:00
ssl Unwind DHE support from BoGo. 2017-04-28 19:38:09 +00:00
third_party Clear the last GTest warning suppression. 2017-02-16 19:03:32 +00:00
tool Make -loop survive errors. 2017-04-17 13:51:18 +00:00
util Move cipher/ into crypto/fipsmodule/ 2017-05-05 22:39:40 +00:00
.clang-format
.gitignore
API-CONVENTIONS.md Fix API-CONVENTIONS.md typos. 2017-01-04 01:46:32 +00:00
BUILDING.md Add the start of standalone iOS build support. 2017-04-07 17:13:44 +00:00
CMakeLists.txt Move bn/ into crypto/fipsmodule/ 2017-05-01 22:51:25 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md Fix FUZZING.md typo. 2017-03-30 16:54:18 +00:00
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: