Google Git
Sign in
boringssl / boringssl / refs/heads/fips-20240407
commit85897d07196b7bf164dbd4673fc78b762aff3e8b[log] [tgz]
authorAdam Langley <agl@imperialviolet.org>Sun May 19 23:41:16 2024 +0000
committerDavid Benjamin <davidben@google.com>Tue May 28 20:33:39 2024 +0000
treef9cc9676c5bc939686f69b84c6b6f9de0c3ae19b
parent5acbee6493035dbf148e44efa14e11e0a2712f50 [diff]
Expose the FIPS module hash at build- and run-time.

In order to provide evidence that a given build is being used when
testing the module (as part of validation), this change prints the
module hash during the build process and makes it available for logging
at run time.

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