Google Git
Sign in
boringssl / boringssl / 7fa475f44d7a38110c285527b9cb4900f68e3ccd
commit7fa475f44d7a38110c285527b9cb4900f68e3ccd[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Apr 07 14:38:57 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Apr 08 12:22:42 2025 -0700
treec874489c158603ce4f145869ae41866a16d63a08
parentef839bf397fb4ecdb66ef2679a08ac7b3563c50b [diff]
Remove ASN1_PRINTABLE

Update-Note: This removes the rather broken ASN1_PRINTABLE type. Note
this has no connection to PrintableString ASN.1 types. Those remain
supported. Code search suggests nothing uses ASN1_PRINTABLE.

X509_NAME still internally uses a variant on this type, though it will
stop using it once we rework it to properly support the values allowed
by the standard.

This removes the ASN1Test.NegativeEnumeratedMultistring test because,
now that ASN1_PRINTABLE is not public API, it is otherwise redundant
with the "Test negative value" test cases in
X509Test.NameAttributeValues.

Bug: 42290275
Change-Id: I78e45eb01b71b369f90603fcd549d3c36b7f3422
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78328
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
5 files changed
tree: c874489c158603ce4f145869ae41866a16d63a08
  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: