Google Git
Sign in
boringssl / boringssl / bd7e4197cdb889f13ce01cf1a029eaa7b6cd6da9
commitbd7e4197cdb889f13ce01cf1a029eaa7b6cd6da9[log] [tgz]
authorMaurice Lam <yukl@google.com>Thu Feb 09 00:28:40 2023 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 10 18:23:28 2023 +0000
treee84d360f269ece1acfa0a2af01ee7747c2fd2668
parent9580424ca8579317d0ccf1d8db5e58539f239a20 [diff]
Generate Rust wrappers for HKDF

This change exposes the necessary APIs for rust-openssl's HKDF wrappers
in [PKeyCtxRef]
(https://docs.rs/openssl/latest/openssl/pkey_ctx/struct.PkeyCtxRef.html#method.set_hkdf_mode).

Diff of the generated bindings: https://gist.github.com/mauricelam/51602bf17d4a5f9023a27cbe5f9ff705

Change-Id: Ic8df3d5308cfee5964ceadd3c2524b77e12512fb
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57066
Reviewed-by: Alex Gaynor <alex.gaynor@gmail.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
1 file changed
tree: e84d360f269ece1acfa0a2af01ee7747c2fd2668
  1. .github/
  2. cmake/
  3. crypto/
  4. decrepit/
  5. fuzz/
  6. include/
  7. rust/
  8. ssl/
  9. third_party/
  10. tool/
  11. util/
  12. .clang-format
  13. .gitignore
  14. API-CONVENTIONS.md
  15. BREAKING-CHANGES.md
  16. BUILDING.md
  17. CMakeLists.txt
  18. codereview.settings
  19. CONTRIBUTING.md
  20. FUZZING.md
  21. go.mod
  22. go.sum
  23. INCORPORATING.md
  24. LICENSE
  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: