-
Notifications
You must be signed in to change notification settings - Fork 3k
Update to Mbed TLS 2.20.0d0 and Mbed Crypto 2.1.0d0 #11687
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
Conversation
@Patater, thank you for your changes. |
#define MBEDTLS_VERSION_STRING "2.19.0" | ||
#define MBEDTLS_VERSION_STRING_FULL "mbed TLS 2.19.0" | ||
#define MBEDTLS_VERSION_NUMBER 0x02130100 | ||
#define MBEDTLS_VERSION_STRING "2.19.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This version doesn't match the one used in other files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Which other files?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you mean the Makefiles, then yes, it doesn't match. We update version.h for official releases and not for developer releases, so in developer releases like 2.20.0d0, we see the most recently released version in version.h.
@Patater I'll review this today, is this ready for integration? |
Started CI |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Thanks. Yes, it is ready. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it affect the PDMC? If so that should be aligned with @JanneKiiskila and @yogpan01
Set to 5.15 |
Description
Update Mbed TLS to 2.20.0d0 and Mbed Crypto to 2.1.0d0.
Pull request type
Reviewers
@AndrzejKurek
Release Notes
What is breaking?
The PSA Crypto secure element (SE) driver API - an additional parameter (a persistent data pointer) is now also passed to the slot validation for the driver to use.
Why is this breaking?
Mbed OS tracks the unstable PSA Crypto API. This particular break is to enable drivers to modify persistent data during slot validation.
Migration
Users implementing SE drivers should add an additional
void *persistent_data
parameter to the slot validation callback, regardless of whether thepersistent_data
will be used or not.psa_drv_se_validate_slot_number_t
did not have a modifiablepersistent_data
parameterpsa_drv_se_validate_slot_number_t
now has a modifiablepersistent_data
parameterNew declaration of
psa_drv_se_validate_slot_number_t
:Old declaration of
psa_drv_se_validate_slot_number_t
: