Google Git
Sign in
boringssl / boringssl.git / ad50a0d7cd457d7ac36dada5bbf5718ec8ff53d4
commitad50a0d7cd457d7ac36dada5bbf5718ec8ff53d4[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu May 11 18:11:07 2017 -0400
committerCQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>Thu May 11 23:30:01 2017 +0000
treea8b8aa89da65e6048c7c30871c1aa6b737464fbd
parent82a83ff577cba9b53f1374474a1e83cebebf71c4 [diff]
Fix diff_asm.go and revert another local MASM perlasm change.

We're not using the MASM output, so don't bother maintaining a diff on
it.

Change-Id: I7321e58c8b267be91d58849927139b74cc96eddc
Reviewed-on: https://boringssl-review.googlesource.com/16246
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>
2 files changed
tree: a8b8aa89da65e6048c7c30871c1aa6b737464fbd
  1. .github/
  2. crypto/
  3. decrepit/
  4. fipsoracle/
  5. fuzz/
  6. include/
  7. infra/
  8. ssl/
  9. third_party/
  10. tool/
  11. util/
  12. .clang-format
  13. .gitignore
  14. API-CONVENTIONS.md
  15. BUILDING.md
  16. CMakeLists.txt
  17. codereview.settings
  18. CONTRIBUTING.md
  19. FUZZING.md
  20. INCORPORATING.md
  21. LICENSE
  22. PORTING.md
  23. README.md
  24. 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: