Skip to content
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

Move to Mbed TLS version 3.0.0 #88

Merged
merged 1 commit into from
Jul 16, 2021
Merged

Conversation

hug-dev
Copy link
Member

@hug-dev hug-dev commented Jul 13, 2021

See #85 for context

@hug-dev hug-dev added the bug Something isn't working label Jul 13, 2021
@hug-dev
Copy link
Member Author

hug-dev commented Jul 13, 2021

This is a breaking change since parameters of methods change. Won't be as easy as doing cargo update to integrate that everywhere.

Copy link
Member

@ionut-arm ionut-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was worried what effect this would have on the TS integration, but it doesn't look like that much changed. Thanks for putting this together!

Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
@hug-dev
Copy link
Member Author

hug-dev commented Jul 13, 2021

The ABI of Mbed Crypto changed from 2.25.0 and 3.0.0 which means that this crate will only be compatible with Mbed TLS 3.0.0 and later versions. This has impact for Parsec stability and for SE driver.

@hug-dev
Copy link
Member Author

hug-dev commented Jul 16, 2021

It was decided to go on with this.

There was a discussion on Mbed TLS mailing list to know more about the API/ABI stability of Mbed Crypto in Mbed TLS.
Until a PSA Crypto compliant version of Mbed Crypto is in an LTS version of Mbed TLS, we can't offer a stable dynamic linking process on this crate. Building from source and statically linking is fine for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants