Roll BoringSSL from 20b18aef7c1a to 29e2ef6cc121 (29 revisions)

https://boringssl.googlesource.com/boringssl.git/+log/20b18aef7c1a..29e2ef6cc121

2025-12-11 davidben@google.com Deduplicate some code to compute test vector paths
2025-12-11 davidben@google.com Skip iovec tests for NIST CAVP vectors
2025-12-11 davidben@google.com Split sealv, openv, and openv_detached into separate tests
2025-12-11 davidben@google.com Recreate the TestIOVecs on every test call
2025-12-10 rpolzer@google.com When testing AEADs, don't split both the AAD and the plaintext.
2025-12-10 davidben@google.com Revert the initial seal/openv implementations
2025-12-10 rpolzer@google.com EVP_AEAD: implement sealv/openv for AES-GCM.
2025-12-10 rpolzer@google.com EVP_AEAD: implement sealv/openv for AES-CTR-HMAC-SHA256.
2025-12-10 divVerent@gmail.com EVP_AEAD: declare CRYPTO_IOVEC based APIs to support zero copy I/O.
2025-12-09 davidben@google.com infra: Remove seemingly unused win_toolchain cache
2025-12-09 davidben@google.com Check in .bazelversion and MODULE.bazel.lock in util/bazel-example
2025-12-09 davidben@google.com infra: Prefix all of BoringSSL's caches
2025-12-09 davidben@google.com Make third_party/benchmark's configure script less noisy
2025-12-09 chlily@google.com Format *.bzl, *.bazel files using buildifier
2025-12-09 chlily@google.com Add a try builder to run boringssl presubmits
2025-12-09 rpolzer@google.com Fix minor benchmark issues:
2025-12-08 davidben@google.com Retire RSA blinding support
2025-12-08 davidben@google.com Benchmark long-lived vs newly-imported RSA keys for both sign and verify
2025-12-08 xfding@google.com Use google/benchmark for performance tracking
2025-12-08 rpolzer@google.com Make the benchmark timeout a floating point, not integer, flag.
2025-12-08 rpolzer@google.com Add a utility to extract identifiers from public headers.
2025-12-08 davidben@google.com Remove non-CBC codepaths from e_tls.cc
2025-12-08 davidben@google.com Don't condition BORINGSSL_self_test on !_MSC_VER
2025-12-08 davidben@google.com Inject the custom libc++ globally
2025-12-08 davidben@google.com Don't build third-party deps with our warnings
2025-12-08 davidben@google.com infra: Bump android-21 to android-24 on CI
2025-12-08 davidben@google.com infra: Disable mac_arm64_bazel builder again
2025-12-08 davidben@google.com Simply warnings config slightly
2025-12-08 davidben@google.com Stop setting -fmsc-version in our build

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: I637f5c08dfb51817aac6d93f00a97279963864f8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/467600
Reviewed-by: Brian Quinlan <bquinlan@google.com>
Reviewed-by: Alexander Aprelev <aam@google.com>
Commit-Queue: Alexander Aprelev <aam@google.com>
1 file changed
tree: 875983fadbcec4bc9a47039ec9775f90c2250f18
  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.