-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Study: Make use of PSA non-optional #5156
Comments
This is more complex than initially thought, for two reasons, both related to backwards compatibility:
|
Does In 4.0, at least one of |
This issue was written a while ago when support for |
Closing in favour of other issues in 4.0 MUST epic |
Entropy is an epic of its own. We have a draft specification (PSA randomness drivers) which we need to implement. If we do it in a minor release then we also have to provide a gradual transition path, if we do it in a major release then we don't and it's a big win. |
Agreed, I was under the impression that entropy was one of our must-haves for 4.0. I think we will want to do some scoping / initial investigation and define that epic soon, possibly in Q4. |
Having configurable entropy sources is a must-have. Switching to the PSA driver system is not strictly a must-have: we can do it independently of accelerator and secure element drivers. But if we don't do that in 4.0 then we have to carry the current entropy interface over to 4.x, and it's not PSA (marketing won't be happy) and it's cumbersome (engineering won't be happy). So I'd strongly prefer if we decide to make it a must-have for 4.0. |
In order to avoid having to maintain two version of the code for each crypto operation in TLS, X.509 and PK, we're making
MBEDTLS_USE_PSA_CRYPTO
active by default.Expected result:
MBEDTLS_PK_C
,MBEDTLS_X509_USE_C
,MBEDTLS_X509_WRITE_C
orMBEDTLS_SSL_TLS_C
is enabled in the build-time configuration, then ``MBEDTLS_USE_PSA_CRYPTOis automatically enabled, as well as enough of
MBEDTLS_PSA_CRYPTO_C` to support it (see comments below).MBEDTLS_USE_PSA_CRYPTO
remains as an option inmbedtls_config.h
, in order to avoid breaking compatibility; documentation is updated to reflect that the user value is now ignored and the value is forced as described above.This task is to study how this could be done while preserving backwards compatibility (see challenges and ideas in the next comment), and make a decision if that's something we want to do - if so, agree on a plan and create a task break down.
The text was updated successfully, but these errors were encountered: