Test TLS connections in Mbed TLS 3.6.0 without psa_crypto_init #9215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Mbed TLS 3.6.0 in the default configuration, and not calling
psa_crypto_init()
, TLS connections fail if they end up negotiating TLS 1.3. See #9210.Status: work in progress — I'm setting up some testing. This is just at the proof-of-concept stage for now: the final form will depend both on how the tests evolve and how we decide to fix the library. My plan:
ssl_client2/ssl_server2
), callpsa_crypto_init
only when needed according to the documentation (including Mbed TLS 3.5 documentation, for backward compatibility). This will cause some test failures in the default configuration when we end up negotiating TLS 1.3 without having calledpsa_crypto_init
.PR checklist