Google Git
Sign in
boringssl / boringssl / 8650dc737d6f719800f1d7702542a423b303f7c8
commit8650dc737d6f719800f1d7702542a423b303f7c8[log] [tgz]
authorPete Bentley <prb@google.com>Mon Oct 09 13:36:25 2023 +0100
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Oct 09 16:03:08 2023 +0000
treee86da1c972751b03325bb67b3a897e128495c93c
parent6d3db84c47643271cb553593ee67362be3820874 [diff]
Fix path for modifiable libcrypto used in KAT testing.

In order to run KATs, we need a copy of libcrypto which won't
abort on integrity check failure, or we'd never get to the KAT.

Previously this was expected to be magically present in the
current directory, but nowawdays we have a build rule for it
so pick it up from the build artifacts.

Change-Id: Ia5359b5369475d94bbde90e81353420a0f1efea2
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/63445
Commit-Queue: Adam Langley <agl@google.com>
Auto-Submit: Pete Bentley <prb@google.com>
Reviewed-by: Adam Langley <agl@google.com>
1 file changed
tree: e86da1c972751b03325bb67b3a897e128495c93c
  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: