Google Git
Sign in
boringssl / boringssl / d0e9c0622792696dce3392b76a1cf9b879a4a34e
commitd0e9c0622792696dce3392b76a1cf9b879a4a34e[log] [tgz]
authorNick Harper <nharper@chromium.org>Tue Aug 13 18:16:05 2024 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 14 16:51:25 2024 +0000
treeebdeb5edc8a6764b4b09856bbf5052d6e2a4b537
parent3529cba4a554fde0ece75a07178c0dd63f73e409 [diff]
Fix documentation missed in 82f9853fc7.

82f9853fc7 replaced ssl_seal_align_prefix_len with two functions,
tls_seal_align_prefix_len and dtls_seal_align_prefix_len. This change
updates documentation that referred to the old ssl_seal_align_prefix_len
function to refer to the correct function.

Change-Id: Ieb8891eff03efc3d894aa56729ae6e47f4be3288
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70207
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: Nick Harper <nharper@chromium.org>
1 file changed
tree: ebdeb5edc8a6764b4b09856bbf5052d6e2a4b537
  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. .bazelignore
  15. .bazelrc
  16. .clang-format
  17. .gitignore
  18. API-CONVENTIONS.md
  19. BREAKING-CHANGES.md
  20. BUILD.bazel
  21. build.json
  22. BUILDING.md
  23. CMakeLists.txt
  24. codereview.settings
  25. CONTRIBUTING.md
  26. FUZZING.md
  27. go.mod
  28. go.sum
  29. INCORPORATING.md
  30. LICENSE
  31. MODULE.bazel
  32. MODULE.bazel.lock
  33. PORTING.md
  34. PrivacyInfo.xcprivacy
  35. README.md
  36. SANDBOXING.md
  37. 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: