Google Git
Sign in
boringssl / boringssl / 62956948e445c5bc67d3f299e0003c34a3030523
commit62956948e445c5bc67d3f299e0003c34a3030523[log] [tgz]
authorDimitri John Ledkov <dimitri.ledkov@surgut.co.uk>Sat May 10 18:16:12 2025 +0100
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 14 09:58:54 2025 -0700
treebc73f04da409a6e76185ba93f78477f7c38f7b11
parent89973806bc2ef652189e157f2736a7d32229c404 [diff]
Increase default salt length from 8 to 16 bytes in PKCS#8 and PKCS#12

Currently, PKCS#8 and PKCS#12 encryption use a salt length of 8 bytes
(64 bits) when no salt length is specified. Increase this default to
16 bytes (128 bits), as recommended by NIST SP 800-132.

Update-Note: PKCS8_encrypt and PKCS8_marshal_encrypted_private_key
will now, if no salt length is specified, default to a salt length of
16 bytes. PKCS12_create will use a salt length of 16 bytes for both
encryption and the MAC.

Fixed: 416889523
Change-Id: I91a496e4856296f07b5445592fb6ecdc41ee718c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79267
Reviewed-by: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
1 file changed
tree: bc73f04da409a6e76185ba93f78477f7c38f7b11
  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: