Google Git
Sign in
boringssl / boringssl / 9e96cc5383e12853cd24cf3442fa691191b2bbf5
commit9e96cc5383e12853cd24cf3442fa691191b2bbf5[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Sep 02 12:34:49 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Sep 03 22:03:47 2025 -0700
tree07d9a57ff14178997ec87e047750ccc289c886a7
parent117f86ef7152be47bd223ac602211a6beb2b1ab9 [diff]
Make X509_verify X509_sign_ctx work with EVP_PKEY_RSA_PSS

Also test that putting an EVP_PKEY_RSA_PSS key in a certificate works...
mostly. X509_get0_pubkey on the resulting object should work but does
not yet. Later work will fix this.

This code also should be reworked to not depend on the big OID table,
but I've left that as a TODO for now.

Bug: 42290364, 384818542
Change-Id: Ifd727cb06ed6c9d1501ef2ef155f4b3c66c8d488
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81782
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
9 files changed
tree: 07d9a57ff14178997ec87e047750ccc289c886a7
  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: