Google Git
Sign in
boringssl / boringssl / c14369ee9a61e77bcafc888a469c48a73ee6022c
commitc14369ee9a61e77bcafc888a469c48a73ee6022c[log] [tgz]
authorBob Beck <bbe@google.com>Fri Feb 07 23:25:48 2025 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Feb 11 12:36:54 2025 -0800
tree2ec2396e05cb296d49f93e0591df0f85ea664bdf
parentbef0b8b4424d029c8460b0d4d390cf93eac12138 [diff]
Make CheckOCSP public api

The rest of OCSP stays internal for the moment, this moves what
is already a reasonable API to validate a stapled OCSP response
out for use external to chrome (as wanted by some consumers outside)

At the moment, the former internal include locations are maintained
and they include the public header. This will be pulled out from
boringssl in a follow on change to this, and then chrome will
be changed once boringssl updates in chrome.

Once chrome is changed, the final follow on CL can land to remove
the internal headers which are now redundant.

Change-Id: I28f12777e9c0cb7ff7affd54c46fecead6c6e398
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76067
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: Bob Beck <bbe@google.com>
10 files changed
tree: 2ec2396e05cb296d49f93e0591df0f85ea664bdf
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .gitignore
  22. API-CONVENTIONS.md
  23. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. 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:

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

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