Roll BoringSSL from 40e035a9e5d7 to db638238d297 (59 revisions)

https://boringssl.googlesource.com/boringssl.git/+log/40e035a9e5d7..db638238d297

2025-09-26 davidben@google.com Tolerate nullptr in i2d_X509_NAME
2025-09-26 davidben@google.com Add some missing includes
2025-09-26 davidben@google.com Fix and test other self-assignment cases in crypto/x509
2025-09-26 chlily@google.com Const-correct all i2d_*_bio functions
2025-09-26 agl@imperialviolet.org Add ACVP modulewrapper for the jitter entropy SHA-384 implementation.
2025-09-26 agl@imperialviolet.org Document that HMAC_Final can have a nullptr `out_len`.
2025-09-25 davidben@google.com Add a missing note about the hashes in ssl_compliance_policy_fips_202205 docs
2025-09-25 poliudian-iv@yandex-team.ru Fix bugs found by clangsa
2025-09-25 davidben@google.com Make setting an X509_NAME to itself work
2025-09-25 davidben@google.com Make the ASN1_TYPE-level type take precedence over the ASN1_STRING one
2025-09-23 davidben@google.com Use CRYPTO_addc_w in bn_from_montgomery_in_place
2025-09-23 davidben@google.com Use a simpler process to compute n0
2025-09-22 chlily@google.com Forbid setting EC public key to point at infinity
2025-09-21 davidben@google.com Remove stale comment
2025-09-21 davidben@google.com Upgrade the opportunistic CRYPTO_sysrand calls to normal ones
2025-09-21 davidben@google.com Remove some stale ifdefs from urandom.cc
2025-09-20 davidben@google.com Reject explicit default X.509 versions and empty extension lists
2025-09-19 davidben@google.com Bump the minimum CMake version to 3.22
2025-09-16 chlily@google.com Add API for configuring client key shares
2025-09-16 davidben@google.com draft-ietf-lamps-x509-policy-graph is now RFC 9618
2025-09-16 davidben@google.com Test a few more unusual TBS certificates
2025-09-16 davidben@google.com Const-correct a bunch more of <openssl/x509.h>
2025-09-16 davidben@google.com Unwind ASN1_ANY_AS_STRING
2025-09-16 davidben@google.com Embed X509_NAME into X509
2025-09-16 davidben@google.com Don't create partial X509 and X509_CRL objects to search the X509_STORE
2025-09-15 davidben@google.com Const-correct X509_NAME and test thread-safety
2025-09-15 davidben@google.com Rewrite the X509_NAME parser
2025-09-15 davidben@google.com Parameterize the tag in IMPLEMENT_EXTERN_ASN1_SIMPLE
2025-09-15 davidben@google.com Test a few more cases of null STACK_OF(T)
2025-09-15 davidben@google.com Make more of atomic<T> available to libcrypto
2025-09-15 davidben@google.com Test that X509_NAME_add_entry will not allow invalid entries to be added
2025-09-15 davidben@google.com Make make_unusual_tbs.go test data idempotent
2025-09-10 davidben@google.com Add EVP_pkey_rsa_pss_sha384 and EVP_pkey_rsa_pss_sha512
2025-09-10 davidben@google.com Store the PSS parameters in the RSA object
2025-09-10 davidben@google.com Don't include every field in every EVP_PKEY_ALG
2025-09-09 chlily@google.com Allow SSL_HANDSHAKE::key_shares to vary in size
2025-09-09 chlily@google.com Always populate supported_group_list
2025-09-09 chlily@google.com Require configured groups for key exchange to be unique
2025-09-07 davidben@google.com Various IWYU fixes
2025-09-06 jonathanjlee@google.com [gtest] Clean up single-arg `testing::Invoke()`s
2025-09-04 davidben@google.com Remove stale static asserts about atomics
2025-09-04 davidben@google.com Add X509_parse_with_algorithms
2025-09-04 davidben@google.com Make X509_verify X509_sign_ctx work with EVP_PKEY_RSA_PSS
2025-09-04 davidben@google.com Rewrite X509's parser with CBS/CBB
2025-09-04 davidben@google.com Rename X509_CINF::signature to X509_CINF::tbs_sig_alg
2025-09-04 davidben@google.com Rewrite X509_PUBKEY's parsers with CBS/CBB
2025-09-04 davidben@google.com Parse X509's signature algorithm with the CBS/CBB functions
2025-09-04 davidben@google.com Parse X509_ALGOR without depending on the templates
2025-09-04 davidben@google.com Make ASN1_EXTERN_FUNCS's parse callback CBS-based
2025-09-04 davidben@google.com Remove the tag parameter to IMPLEMENT_EXTERN_ASN1
2025-09-04 davidben@google.com Add X509_ALGOR_copy
2025-09-04 davidben@google.com Write some templated functions for the d2i/i2d convention
2025-09-04 davidben@google.com Make CBS/CBB-versions of crypto/asn1 types
2025-09-04 davidben@google.com Avoid one malloc indirection in X509
2025-09-03 davidben@google.com Test the implicit cleanup feature of X509_sign_ctx, etc.
2025-09-03 davidben@google.com Add a benchmark for parsing with d2i_X509
2025-09-03 davidben@google.com Systematically test that parsers catch trailing data
2025-09-03 davidben@google.com Test verifying signatures over "unusual" TBSCertificates
2025-09-03 davidben@google.com Use std::string_view in x509_test.cc

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/boringssl-dart-sdk
Please CC dart-engprod@google.com,dart-vm-gardener@grotations.appspotmail.com,dart-vm-team@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in BoringSSL: https://crbug.com/boringssl/new
To file a bug in Dart SDK: https://github.com/dart-lang/sdk/issues

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Tbr: dart-vm-gardener@grotations.appspotmail.com
Change-Id: I3007be42a120096e0f0027cbc6acb7504f0c4f94
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451842
Commit-Queue: Ryan Macnak <rmacnak@google.com>
Reviewed-by: Ryan Macnak <rmacnak@google.com>
Reviewed-by: Alexander Aprelev <aam@google.com>
1 file changed
tree: e8299806b7e6590e791b2dce088066ff87127b13
  1. .dart_tool/
  2. .github/
  3. benchmarks/
  4. build/
  5. docs/
  6. pkg/
  7. runtime/
  8. samples/
  9. sdk/
  10. tests/
  11. third_party/
  12. tools/
  13. utils/
  14. .clang-format
  15. .gitattributes
  16. .gitconfig
  17. .gitignore
  18. .gn
  19. .mailmap
  20. .style.yapf
  21. AUTHORS
  22. BUILD.gn
  23. CHANGELOG.md
  24. codereview.settings
  25. CONTRIBUTING.md
  26. DEPS
  27. LICENSE
  28. OWNERS
  29. PATENT_GRANT
  30. PRESUBMIT.py
  31. pubspec.yaml
  32. README.dart-sdk
  33. README.md
  34. sdk.code-workspace
  35. sdk_args.gni
  36. sdk_packages.yaml
  37. SECURITY.md
  38. WATCHLISTS
README.md

Dart

An approachable, portable, and productive language for high-quality apps on any platform

Dart is:

  • Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.

  • Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.

  • Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.

Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:

  • Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.

  • Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).

Dart platforms illustration

License & patents

Dart is free and open source.

See LICENSE and PATENT_GRANT.

Using Dart

Visit dart.dev to learn more about the language, tools, and to find codelabs.

Browse pub.dev for more packages and libraries contributed by the community and the Dart team.

Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).

Building Dart

If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.

There are more documents in our repo at docs.

Contributing to Dart

The easiest way to contribute to Dart is to file issues.

You can also contribute patches, as described in Contributing.

Roadmap

Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.