kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4,463 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
af2b1e8210
Go to file
David Benjamin af2b1e8210 C++ headers should be more aggressively wrapped in extern "C++". 
This is kind of a mess. Some projects will wrap our public headers in
extern "C", so we use extern "C++" around our C++ APIs. However this
needs to be done when including C++ standard library headers too since
they don't always, themselves, guard against being wrapped in extern
"C".

Change-Id: Ib7dd4a6f69ca81dd525ecaa1418b3b7ba85b6579
Reviewed-on: https://boringssl-review.googlesource.com/18504
Reviewed-by: Adam Langley <agl@google.com>
2017-07-27 20:12:53 +00:00
.github
crypto x86_64 assembly pack: "optimize" for Knights Landing, add AVX-512 results. 2017-07-26 22:01:37 +00:00
decrepit
fipstools Have run_cavp.go create “resp” directories as needed. 2017-06-08 19:13:01 +00:00
fuzz Refresh TLS fuzzer corpora. 2017-07-14 20:21:33 +00:00
include/openssl C++ headers should be more aggressively wrapped in extern "C++". 2017-07-27 20:12:53 +00:00
infra/config Restore ios64_compile to the CQ. 2017-05-11 16:49:08 +00:00
ssl Make ranged for loops work with STACK_OF(T). 2017-07-26 22:02:00 +00:00
third_party Fix build with VS 2017. 2017-06-07 18:56:06 +00:00
tool Fix bssl sockets on Windows. 2017-07-25 19:03:16 +00:00
util x86_64 assembly pack: "optimize" for Knights Landing, add AVX-512 results. 2017-07-26 22:01:37 +00:00
.clang-format
.gitignore Add sde-linux64 to .gitignore. 2017-05-12 14:53:07 +00:00
API-CONVENTIONS.md
BUILDING.md Set static armcaps based on __ARM_FEATURE_CRYPTO. 2017-06-09 00:29:10 +00:00
CMakeLists.txt Add a CMake toggle to allow the C++ runtime. 2017-07-26 15:51:43 +00:00
codereview.settings
CONTRIBUTING.md
FUZZING.md Fix typo in FUZZING.md. 2017-07-06 18:25:07 +00:00
INCORPORATING.md
LICENSE
PORTING.md Document our strict behaviour when clients attempt renegotiation. 2017-07-25 21:41:25 +00:00
README.md
sources.cmake Implement scrypt from RFC 7914. 2017-06-12 20:32:21 +00:00
STYLE.md Add text about build logic to the style guide. 2017-07-06 01:38:28 +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: