Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/1ef0e676bf400a1d4d2ebd10f97d155bc277c4cc
commit
1ef0e676bf400a1d4d2ebd10f97d155bc277c4cc
[log]
author
Gilles Peskine <Gilles.Peskine@arm.com>
Wed Jan 07 16:01:19 2026 +0100
committer
Gilles Peskine <Gilles.Peskine@arm.com>
Mon Feb 09 18:04:13 2026 +0100
tree
26f2ded4e40bc6b041adc54ce76f8f6e46e65625
parent
e9f66f7ec225cabda0fd1f12acc3019295e721bf [diff]
Add all mechanisms up to PSA Crypto API 1.4

Define the necessary new categories (key wrap, key encapsulation, XOF).

This completes the list of mechanisms in the PSA Crypto API version 1.4,
except for PAKE that are more challenging (family parametrization, need to
find sample keys in `asymmetric_key_data.py`), and except for the PQC
extension.

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
2 files changed
tree: 26f2ded4e40bc6b041adc54ce76f8f6e46e65625
  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.