Google Git
Sign in
boringssl / boringssl.git / 2a187a43169ec4855f549972e01b7b34d704be41
commit2a187a43169ec4855f549972e01b7b34d704be41[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Apr 11 17:26:50 2016 -0400
committerDavid Benjamin <davidben@google.com>Mon Apr 11 17:26:50 2016 -0400
treed25df9eb215faf1de707d296a1bad4690ad41623
parent14420e91e0d6b5e2b5d2c39b2315151ae5837fb1 [diff]
No-op change to test bugdroid.

Making sure the BUG= line works correctly.

BUG=41

Change-Id: Icedf5f1ec8211696c74d9e9f9d322483c43444fc
tree: d25df9eb215faf1de707d296a1bad4690ad41623
  1. .github/
  2. crypto/
  3. decrepit/
  4. fuzz/
  5. include/
  6. ssl/
  7. tool/
  8. util/
  9. .clang-format
  10. .gitignore
  11. BUILDING.md
  12. CMakeLists.txt
  13. codereview.settings
  14. CONTRIBUTING.md
  15. FUZZING.md
  16. LICENSE
  17. PORTING.md
  18. README.md
  19. STYLE.md
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: