Google Git
Sign in
boringssl / boringssl / f575d9b3632cc6bcaa14e8bb0328c9f68579a342
commitf575d9b3632cc6bcaa14e8bb0328c9f68579a342[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Jun 08 13:33:00 2022 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jun 08 17:57:19 2022 +0000
treedaf5ddca7c3fbe04812338f30a8bafd7b6fbe405
parent4566bb5fe517f7f141b5fe935c559fc4311af35d [diff]
Add X509_REQ_set1_signature_algo and X509_REQ_set1_signature_value.

These are the X509_REQ analogs to
https://boringssl-review.googlesource.com/c/boringssl/+/43784 and
https://boringssl-review.googlesource.com/c/boringssl/+/47525.

The one difference is CSRs do not have the redundant copy of the
signature algorithm, so X509_REQ_set1_signature_algo is a little
simpler.

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