pki: Limit MTC CA IDs to 32 bytes

draft-ietf-plants-merkle-tree-certs-07, Section 5.1, defines an MTC CA
ID as a trust anchor ID, which draft-ietf-tls-trust-anchor-ids-06 limits
to 32 bytes in its binary (RELATIVE-OID contents) representation.

Enforce this limit in ParseMtcCaInfo and EncodeMtcCaCertificate,
matching crypto/x509
(https://boringssl-review.googlesource.com/c/boringssl/+/103948).

Bug: 575507260
Change-Id: Ib0870c0e8f59e57a2c8a57c6ff4943f36a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/106169
Auto-Submit: Lily Chen <chlily@google.com>
Reviewed-by: Matt Mueller <mattm@google.com>
Commit-Queue: Matt Mueller <mattm@google.com>
Presubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>
6 files changed
tree: 7fbeafb1f03ddb758c08ab5e16b8831543033f6d
  1. .bcr/
  2. .github/
  3. _agents/
  4. bench/
  5. cmake/
  6. crypto/
  7. decrepit/
  8. docs/
  9. fuzz/
  10. gen/
  11. include/
  12. infra/
  13. pki/
  14. rust/
  15. ssl/
  16. third_party/
  17. tool/
  18. util/
  19. .bazelignore
  20. .bazelrc
  21. .bazelversion
  22. .clang-format
  23. .clang-format-ignore
  24. .clangd
  25. .gitattributes
  26. .gitignore
  27. API-CONVENTIONS.md
  28. AUTHORS
  29. BREAKING-CHANGES.md
  30. BUILD.bazel
  31. build.json
  32. BUILDING.md
  33. CMakeLists.txt
  34. codereview.settings
  35. CONTRIBUTING.md
  36. FUZZING.md
  37. go.mod
  38. go.sum
  39. INCORPORATING.md
  40. LICENSE
  41. MODULE.bazel
  42. MODULE.bazel.lock
  43. PORTING.md
  44. PRESUBMIT.py
  45. PrivacyInfo.xcprivacy
  46. README.md
  47. SANDBOXING.md
  48. SECURITY.md
  49. 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: