Add crypto configuration components by ronald-cron-arm · Pull Request #769 · Mbed-TLS/TF-PSA-Crypto

ronald-cron-arm · 2026-04-20T08:54:50Z

Description

Add the equivalent of all Mbed TLS components-configuration-crypto.sh but:

the components based on and related to libtestdriver1
the depends.py components (see DI: split depends.py mbedtls-docs#201)
a few other components, see the commit "Remove various config crypto components"

Only 14 commits to review starting from ab99f98 (merge commit to get the Mbed TLS components-configuration-crypto.sh components and their history into TF-PSA-Crypto).

PR checklist

changelog not required because: expending testing
framework PR not required
TF-PSA-Crypto development PR provided here
TF-PSA-Crypto 1.1 PR provided # TODO
mbedtls development PR not required because: will remove some components in Mbed TLS components-configuration-crypto.sh independently
mbedtls 4.1 PR not required because: will remove some components in Mbed TLS components-configuration-crypto.sh independently
mbedtls 3.6 PR not required because: n/a
tests provided

At initialization, set the verify_result field of the ssl session to MBEDTLS_X509_VERIFY_NOT_STARTED, rather than 0 as it is by default currently. This prevents mbedtls_ssl_get_verify_result() from indicating that certificate verification has passed if it is called prior to the handshake happening. Signed-off-by: David Horstmann <david.horstmann@arm.com>

Write a testcase to get verify_result before we have performed a handshake and make sure that it is initialised to a failure value. Signed-off-by: David Horstmann <david.horstmann@arm.com>

Signed-off-by: David Horstmann <david.horstmann@arm.com>

Since we explicitly document the value 0xFFFFFFFF or -1u as representing 'result not available', we can use it as a sensible default value without creating an API change. Use this value instead of introducing a new verification result value. Signed-off-by: David Horstmann <david.horstmann@arm.com>

Initialize the verify_result field in mbedtls_ssl_session_free(). Previously we were just zeroising the entire session object, which would yield a default 'success' value if the same object were reused. Test that this initialisation is actually happening by setting verify_result manually to zero and calling mbedtls_ssl_session_free() on the session before checking its value. Signed-off-by: David Horstmann <david.horstmann@arm.com>

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

Signed-off-by: Janos Follath <janos.follath@arm.com>

The generated unit tests have the input parameters in large stack buffers and therefore ASan doesn't notice under or overflows in them. Copy the input parameter into a locally allocated buffer to trigger ASan if something goes wrong. Signed-off-by: Janos Follath <janos.follath@arm.com>

The flawed condition made us accept invalid IPv6 addresses and in some cases lead to a buffer underread. Signed-off-by: Janos Follath <janos.follath@arm.com>

Signed-off-by: Janos Follath <janos.follath@arm.com>

We were accidentally running the check in TF-PSA-Crypto instead of in Mbed TLS. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

…TLS 1.2 TLS-PRF uses either SHA-256 and SHA-384, so the removed paragraph was not correct. The correct version is already available few lines below in the same header file. Signed-off-by: Valerio Setti <valerio.setti@nordicsemi.no>

…erated_files-mbedtls-actually_check_mbedtls Actually check committed generated files

When we are using PSK or when authmode == MBEDTLS_SSL_VERIFY_NONE, we intentionally do not verify the certificate. In these cases, do not keep verify_result at -1u but set it to MBEDTLS_X509_BADCERT_SKIP_VERIFY to indicate that no certificate verification took place. Signed-off-by: David Horstmann <david.horstmann@arm.com>

Fix buffer underflow in `x509_inet_pton_ipv6()`

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

We do not return failure, but return -1u which is documented as a value that indicates that the result is not available. Signed-off-by: David Horstmann <david.horstmann@arm.com>

…-4.0 Minor improvements to bump_version.sh

In the TLS-Exporter for TLS 1.3 we mistakenly call PSA_HASH_LENGTH() on an mbedtls_md_type_t when it should be called on a psa_algorithm_t. Fortunately, these two types have almost the same values, since we have previously aligned them to make conversion more efficient. As a result, PSA_HASH_LENGTH() produces exactly the same value when called on an mbedtls_md_type_t as with the equivalent psa_algorithm_t. Thanks to this happy coincidence, fix a largely cosmetic issue (rather than a major functional bug). Signed-off-by: David Horstmann <david.horstmann@arm.com>

…0260216 Update submodules

…nversion-tls-exporter Fix missing type conversion in the TLS-Exporter