kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
1,909 Commits 12 Branches 0 Tags 38 MiB
C 43.1%
C++ 23.5%
Go 13.6%
Raku 10.8%
Perl 4%
Other 4.9%
60be027625
Go to file
David Benjamin 60be027625 Style: fix some header guards 
Change-Id: I86c30c7fe489c720f83f744696df0a0a20268531
Reviewed-on: https://boringssl-review.googlesource.com/6317
Reviewed-by: Adam Langley <alangley@gmail.com>
2015-10-26 18:47:51 +00:00
crypto Fix comment style in crypto/rand/rand.c. 2015-10-26 17:58:08 +00:00
decrepit Move arm_arch.h and fix up lots of include paths. 2015-08-26 01:57:59 +00:00
include/openssl Style: fix some header guards 2015-10-26 18:47:51 +00:00
ssl Document the rest of ssl.h. 2015-10-26 18:43:38 +00:00
tool Deprecate SSL_library_init. 2015-10-26 18:36:23 +00:00
util Linkify pipe words. 2015-10-26 18:46:53 +00:00
.clang-format Inital import. 2014-06-20 13:17:32 -07:00
.gitignore Fix documentation generation on Windows. 2015-08-19 00:45:42 +00:00
BUILDING.md Allow ARM capabilities to be set at compile time. 2015-10-20 22:40:15 +00:00
CMakeLists.txt Silence MSVC warning C4210. 2015-10-13 18:20:29 +00:00
codereview.settings Add a codereview.settings file. 2014-11-18 22:21:33 +00:00
LICENSE Note that some files carry in Intel license. 2015-07-28 00:55:32 +00:00
PORTING.md Deprecate SSL_library_init. 2015-10-26 18:36:23 +00:00
README.md Links in README.md, take two. 2015-10-13 18:04:43 +00:00
STYLE.md Markdown-ify STYLE. 2015-09-03 18:37:39 +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:

  • PORTING.md: how to port OpenSSL-using code to BoringSSL.
  • BUILDING.md: how to build BoringSSL
  • STYLE.md: rules and guidelines for coding style.
  • include/openssl: public headers with API documentation in comments. Also available online.