Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/650159869a381d4c47695620a49dd85824f9c254
commit
650159869a381d4c47695620a49dd85824f9c254
[log]
author
Ronald Cron <ronald.cron@arm.com>
Tue Jan 20 11:12:21 2026 +0100
committer
Ronald Cron <ronald.cron@arm.com>
Fri Jan 23 21:02:16 2026 +0100
tree
d54e19973553daed2bf92bd0707f7e5c75c238b7
parent
5639bf9a6983911b5bc11b838354b7a9dbf3e5da [diff]
tls_handshake_tests.py: Add no-tls12-client-hello-defragmentation-support arg

Add a no-tls12-client-hello-defragmentation-support
argument to specify if TLS 1.2 Client Hello
defragmentation is fully supported or not.
This is temporary while the support is being added
in Mbed TLS development and 3.6 branches.

Signed-off-by: Ronald Cron <ronald.cron@arm.com>
2 files changed
tree: d54e19973553daed2bf92bd0707f7e5c75c238b7
  1. .github/
  2. data_files/
  3. docs/
  4. history/
  5. psasim/
  6. scripts/
  7. tests/
  8. .gitignore
  9. CMakeLists.txt
  10. CONTRIBUTING.md
  11. dco.txt
  12. exported.make
  13. LICENSE
  14. README.md
README.md

Mbed TLS framework

This repository contains a version-independent build and test framework for TF-PSA-Crypto and Mbed TLS.

You need this repository as a Git submodule in a branch of one of the above repositories if:

  • You want to build, test or contribute to Mbed TLS 3.6.0 or above, and you are working from a snapshot of a Git commit on a development branch.
  • You want to build, test or contribute to TF-PSA-Crypto, and you are working from a snapshot of a Git commit on a development branch.

You do not need this repository if:

  • You are working with Mbed TLS 2.28.
  • You want to build a release of Mbed TLS and run its unit tests.

Contributing

We gratefully accept bug reports and contributions from the community. Please see the contributing guidelines for details on how to do this.

License

Unless specifically indicated otherwise in a file, Mbed TLS framework files are provided under a dual Apache-2.0 OR GPL-2.0-or-later license. See the LICENSE file for the full text of these licenses, and the ‘License and Copyright’ section in the contributing guidelines for more information.