Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/4c54ebd97d9ad87ff69a0e2a50ef8fc61eb835c5
commit
4c54ebd97d9ad87ff69a0e2a50ef8fc61eb835c5
[log]
author
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Jan 08 15:30:56 2026 +0100
committer
Gilles Peskine <Gilles.Peskine@arm.com>
Mon Feb 09 18:04:13 2026 +0100
tree
e929d0d9fe99e6ef9bdc2344b5b64184ec03cacc
parent
987737675a31c2230dfccebe66d64fa5b621c300 [diff]
OpFail: only consider categories in which at least one algorithm is supported

Addresses https://github.com/Mbed-TLS/mbedtls-framework/issues/264
but perhaps not in the best way.

Keep an exception for PAKE, for which we already have algorithm
support (`PSA_ALG_JPAKE`) but no `pake_fail` function.
https://github.com/Mbed-TLS/mbedtls-framework/issues/263

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
1 file changed
tree: e929d0d9fe99e6ef9bdc2344b5b64184ec03cacc
  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.