Google Git
Sign in
boringssl / boringssl / d94be4172325d0ac239ef3046d2c609aebeaf00a
commitd94be4172325d0ac239ef3046d2c609aebeaf00a[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Oct 10 11:00:52 2023 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Oct 10 16:41:03 2023 +0000
tree4e8bd40536a9a6ee19187d8575cb7c579a9e1ed1
parentb975f12a2fa3f313b98b0dc40a9bc9e8c0667d08 [diff]
Update tools on CI

Also document in comments why the NDK cannot be updated right now. The
libc++ update requires configuring PSTL. I matched Chromium in
https://chromium-review.googlesource.com/c/chromium/src/+/4864131

Change-Id: Ic374a8a95f9f6f23266704d69c11b835cd718d94
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63505
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
3 files changed
tree: 4e8bd40536a9a6ee19187d8575cb7c579a9e1ed1
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. pki/
  8. rust/
  9. ssl/
  10. third_party/
  11. tool/
  12. util/
  13. .clang-format
  14. .gitignore
  15. API-CONVENTIONS.md
  16. BREAKING-CHANGES.md
  17. BUILDING.md
  18. CMakeLists.txt
  19. codereview.settings
  20. CONTRIBUTING.md
  21. FUZZING.md
  22. go.mod
  23. go.sum
  24. INCORPORATING.md
  25. LICENSE
  26. PORTING.md
  27. README.md
  28. SANDBOXING.md
  29. sources.cmake
  30. 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.

Project links:

There are other files in this directory which might be helpful: